On Sun, Oct 28, 2012 at 12:15 PM, Karl Denninger wrote:
> 4. pg_start_backup('Upgrading') and rsync the master to the NEW slave
> directory ex config files (postgresql.conf, recovery.conf and pg_hba.conf,
> plus the SSL keys if you're using it). Do NOT rsync pg_xlog's contents or
> the WAL archiv
On 10/25/2012 9:12 AM, delongboy wrote:
> I brought down the master then the slave and upgraded both. Then I did the
> rsync and brought both up.. This worked. However with the database being
> very large it took quite a while. It seemed rsync had to make a lot of
> changes.. this surprised me.
Daniel Burbridge writes:
> I have a problem with prepared statements choosing a bad query plan - I was
> hoping that 9.2 would have eradicated the problem :(
9.2 will only pick the "right" plan if that plan's estimated cost is a
good bit cheaper than the "wrong" parameterized plan. In this case
I have a problem with prepared statements choosing a bad query plan - I was
hoping that 9.2 would have eradicated the problem :(
Taken from the postgresql log:
<2012-10-23 15:21:03 UTC acme_metastore 13798
5086b49e.35e6> LOG: duration: 20513.809 ms execute S_6:
I brought down the master then the slave and upgraded both. Then I did the
rsync and brought both up.. This worked. However with the database being
very large it took quite a while. It seemed rsync had to make a lot of
changes.. this surprised me. I thought they would be almost identical.
But
