Scott Marlowe wrote:
> On Wed, Aug 27, 2008 at 10:58 AM, Andrew Sullivan <[EMAIL PROTECTED]> wrote:
> > On Tue, Aug 26, 2008 at 08:46:33PM -0400, Lew wrote:
> >> upgrades to PG, it is our duty to inform our bosses of the risk of not
> >> upgrading, so they can properly assess risks and manage them
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.
Could it be the compile time setting? I guess you can try
# pg_config --configure
and the --prefix=... will like
On Fri, Sep 5, 2008 at 12:44 PM, Carol Walter <[EMAIL PROTECTED]> wrote:
> 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 o
If I recall correctly, the reason we originally set autovacuum_freeze_max_age =
2,000,000,000 was that most of the data in the DB is a rolling
window(partitioned tables) and so by having the max age so high most of the
tables in the DB would never need to be vacuumed at all thus allowing the
au
Carol Walter <[EMAIL PROTECTED]> writes:
> I can't figure out how the Postgres that's running on the production
> web server knows where to look for its data.
Generally the location of the data directory is determined by a -D
switch on the postmaster command line, or by setting the PGDATA
enviro
Arctic Toucan <[EMAIL PROTECTED]> writes:
> My standard settings in the config file are:
> autovacuum_freeze_max_age = 2,000,000,000
> vacuum_freeze_min_age = 100,000,000
Ah, well, there's the issue. It could be expected that no tuple
freezing would happen before autovacuum_freeze_max_age. I'd t
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 th
OK, I am glad to hear that what I thought might be the problem is fixed in PG
8.2. I feel much better about that :-)
That must mean there was something unusual about this particular DB. I have
several other "cloned" DB's configured the same way(They haven't failed over
yet), and checking the a
Arctic Toucan <[EMAIL PROTECTED]> writes:
> 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 vacuu
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 transp
"Claus Guttesen" <[EMAIL PROTECTED]> writes:
> I have a table with a serial field defined with an older version of
> postgresql (ver. 7). Back then max_value was 2147483647:
> How can I increase it? By updating the max_value-field?
I think you're looking for ALTER SEQUENCE.
Note that if the colum
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
On Thu, Sep 4, 2008 at 4:50 PM, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 4, 2008 at 2:42 PM, slamp slamp <[EMAIL PROTECTED]> wrote:
>> 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
On Fri, Sep 5, 2008 at 6:58 AM, Claus Guttesen <[EMAIL PROTECTED]> wrote:
> 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 c
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 chang
> Datum: Thu, 04 Sep 2008 22:01:51 -0400
> Von: Andriy Bakay <[EMAIL PROTECTED]>
> An: Jan-Peter Seifert <[EMAIL PROTECTED]>
> CC: pgsql-admin@postgresql.org, [EMAIL PROTECTED]
> Betreff: Re: [ADMIN] SSL problems
> After I disable SSL option in postgresql.conf the server is starting
> successf
16 matches
Mail list logo
