rally drop their privs as soon as possible (eg. Apache).
--
Stuart Bishop <[EMAIL PROTECTED]>
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
8.3 -> 8.4) require a full dump & reload
on all platforms or using 3rd party replication tools like Slony-I.
I have no idea about OpenSuSE's packages.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
eports or recommendations,
pay attention to the platform and implementation rather than the
protocol.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
that the diff of the before and after schemas checks out. If you screw
up, you can end up with crazy things like multiple indexes with the
same name and other stuff making your database unrecoverable.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-admin mailing list (pgsql-a
ier like "base_txrecords".
This doesn't help when your backup skips them because the files exist
on another disk partition. Out of sight, out of mind.
If pg_basebackup defaulted to --xlog and its use was encouraged these
mistakes might be less common.
--
Stuart Bishop
http://ww
standby of ServerB, start it up.
Does this look correct to people?
Am I going to end up in trouble copying files into pg_xlog like this on a
busy system?
Is it overengineered? eg. will a master ensure everything is streamed to
connected hot standbys before a graceful shutdown?
--
will tell you by how much.
--
Stuart Bishop
http://www.stuartbishop.net/
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
