ok - I'll set these up on our test machine. I'm not rebooting either -
just sending a reload.
Kevin Grittner wrote:
"Maria L. Wilson" wrote:
thanks Kevin - will any statements resulting in errors be logged
no matter how long they take?
I believe so, but my naturally paranoid nat
"Maria L. Wilson" wrote:
> thanks Kevin - will any statements resulting in errors be logged
> no matter how long they take?
I believe so, but my naturally paranoid nature always has me testing
such things before I roll them to production. ;-)
It's always possible I misunderstood or overlook
thanks Kevin - will any statements resulting in errors be logged no
matter how long they take?
Maria-
Kevin Grittner wrote:
"Maria L. Wilson" wrote:
log_statement = 'all' # none, ddl, mod, all
Try setting this to 'none'.
-Kevin
"Maria L. Wilson" wrote:
> log_statement = 'all' # none, ddl, mod, all
Try setting this to 'none'.
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Trying to do some modifications to the amount of logging that our
postgres database server (8.4 on linux) does on our production servers
and had a few questions that I hope someone would clear up.
Basically - in production, it would be nice to limit some of the logging
and let the dev/test dat
On Tue, 2010-05-11 at 09:16 -0400, Ray Stell wrote:
> What are the steps for upgrade of a primary/PITR standby pair to the
> latest 8.3 patchset, 8.3.6-8.3.10? I don't see this in the docs.
> Should there be something added to 15.4. Upgrading?
>
> My guess is:
> 1. turn off the standby confi
What are the steps for upgrade of a primary/PITR standby pair to the
latest 8.3 patchset, 8.3.6-8.3.10? I don't see this in the docs.
Should there be something added to 15.4. Upgrading?
My guess is:
1. turn off the standby config in primary
2. upgrade primary
3. rebuild standby
That way you
