Hello,

We're building a test box for our webmaster to play in. It needs to
have the same config as his production box. The postgres default
data directory doesn't match the location of the data directory
location on the production box. The postgresql.conf file has the
line that says that it changes the default data location commented
out. Is there somewhere else that postgres can get this information?

I can't figure out how the Postgres that's running on the production
web server knows where to look for its data.

Thanks,
Carol

Hi,

I'm looking at converting some databases from SQL_ASCII to UTF8. The
conversion worked fine in tests, so I'm not overly concerned about the
data. What I'm wondering is if there is from the client side I should
be worried about (ie - different query plans being chosen), or should it
be transparent to the application.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.

I have a fairly large database(approx. 1.5TB) that is backed up by a warm standby database using log shipping(PITR). This setup had been running for a couple of months when I ran into a problem on the primary DB and had to failover to the standby DB. This worked as expected.

Shortly thereafter(Sometime over the long weekend of course), Postgres shutdown the database to avoid XID wraparound data loss. I presume there were warnings in the log about running out of XIDs, but nobody noticed in time and given what transpired after that I don't think it would have mattered if they had.

As per the documentation, I started the DB in single user mode and attempted to do a full database vacuum. After this ran for about 12hours the pg_xlog directory ran out of disk space. I'm not sure I understand why anything is written to pg_xlog as part of the vacuum process, perhaps someone can enlighten me.

I next started looking at the age(refrozenxid) of the tables in my DB, and was surprised to see that over 4000 of the 5000 tables in this DB had an age over 2Billion. So thats 4000 tables representing over a terabyte of data that need to be vacuumed! I am now vacuuming those tables one at a time, which is taking a long time(This is a scripted process). So there is no way I could have vacuumed the tables quickly enough even given a warning of impending XID wraparound.

Looking through the support mailing lists(Bugs) I see some discussion about the frozenxid updates on the master not being propogated to the slave through the WAL logs, and comments from Tom, Alvaro and Heikki suggesting that they were looking into a solution for PG 8.3 and needed a way around the problem in PG 8.2.

I am currently running PG 8.2.4 on FreeBSD.

So my questions are:

1) What is the recommended way to either solve or get around this problem in PG 8.2.4?
2) Is this "problem" fixed in some more current version of Postgres? I didn't see any mention of it in release notes up to PG 8.3.3?
3) Does this mean that if you are trying to use a warm standby DB with PITR, you need to make a new base backup of your primary DB every 1.5billion transactions, or there abouts, to avoid the problem. If so, I think this should be documented in the "Caveats" section of "Continuous Archiving and Point-in-time-recovery(PITR)" section of the manual.

Regards...

Mark Sherwood

_________________________________________________________________

Hi.

I have a table with a serial field defined with an older version of
postgresql (ver. 7). Back then max_value was 2147483647:

select max_value from my_bid_seq ;
max_value
------------
2147483647

How can I increase it? By updating the max_value-field? This is an
older thread and may have changed:
http://archives.postgresql.org/pgsql-admin/2002-12/msg00033.php

I'm running postgresql 8.3.1.

--
regards
Claus

When lenity and cruelty play for a kingdom,
the gentler gamester is the soonest winner.

Shakespeare

Okay - this was to make sure, that SSL actually really IS the problem. As Tom Lane already mentioned - get your installation to talk to you. pg_ctl should always throw an explaining error message if the server can't be started. In my case with SSL often incorrect privileges on files and/or missing files.
I guess you already have "log_destination = 'stderr'" and "logging_collector = on" enabled in your postgresql.conf ...
If I remember correctly sometimes non-matching versions of PostgreSQL and OpenSSL might be a reason too.

Peter

hi,

we are newto pg, one of our developers is asking how we can tap the
user roles of pg.  what table to look at?  we have a functionality
requirement that an application will behave according to his roles?

thank you,

oca

hi,we are newto pg, one of our developers is asking how we can tap the
user roles of pg.  what table to look at?  we have a functionality requirement
that an application will behave according to his roles?thank
you,oca

Rolex Submariner Watches: Quality Rolex Discount Watches

Quality Rolex Submariner Watches http://rolex-watches.pxhelp.com/rolex-submariner.html

Thank you for choosing http://www.pxhelp.com/

Discount Rolex Watches http://rolex-watches.pxhelp.com/

We guarantee our Rolex Submariner Watches and Rolex Submariner Luxury
Watches aren't just a simple imitation. We use the same fine materials
and technology that the original does. Each Rolex Submariner Watch
produced is examined carefully by our quality test department and
every watch is inspected again before being moved out from our
warehouse. It is our heartfelt desire that you do experience the joy
of shopping when buying one of our Rolex Watches at our site
http://www.pxhelp.com/ . We guarantee high quality and favorable price
we offer. Best service you will receive from us. Any question please
contact with us, we are happy to service for you.

Rolex Submariner Watches Items :

Rolex Oyster Perpetual Submariner Date Mens Watch 16613-BLSO
http://rolex-watches.pxhelp.com/Rolex-wristwatch-6090.html
Rolex Oyster Perpetual Submariner Date Mens Watch 16613-GYDO
http://rolex-watches...

ok i managed to get this to work. however i still get the "Repository
pgdg82 is listed more than once in the configuration", this is
probably a rhel yum bug.

On Thu, Sep 4, 2008 at 4:12 PM, slamp slamp gmail.com> wrote:

Chopard Happy Sport Diamond Steel Ladies Watch 27/8280-23/11
Recommendation Discount Watches

Chopard Happy Sport Diamond Steel Ladies Watch 27/8280-23/11 Site:
http://chopard-watches.pxhelp.com/Chopard-wristwatch-1768.html

Thank you for choosing http://www.pxhelp.com/

Quality Chopard Watches: http://chopard-watches.pxhelp.com/

Chopard Happy Sport Diamond Steel Ladies Watch 27/8280-23/11
AdditionalInfo :

Hello,

I am working with a PostgreSQL Database and I want to change the Filesystem to ZFS.

Does someone have experience with PostgreSQL and its Performance with ZFS? Are the current write options for PostgreSQL suitable for ZFS?

Do I need to finetune Postgres with the settings for ZFS?
Like finetuning of...
- fsync
- wal_sync_method

Thanks if someone can help me on this.

Cheers Thomas