Hello,
I made a bad update to search_path, which basically had line returns:
prod_candidate=# alter user postgres set search_path to 'search_path=public,
schemprod_candidate'# a1, schema2, schema3'prod_candidate-# ;ALTER ROLE
And now, I can't get it to insert correctly again, there always seems
On 8 July 2013 14:40, Colin S colin_sl...@hotmail.com wrote:
Hello,
I made a bad update to search_path, which basically had line returns:
prod_candidate=# alter user postgres set search_path to
'search_path=public, schem
prod_candidate'# a1, schema2, schema3'
prod_candidate-# ;
ALTER
Date: Mon, 8 Jul 2013 14:46:29 +0200
Subject: Re: [ADMIN] search_path update weirdness
From: mabew...@gmail.com
To: colin_sl...@hotmail.com
CC: pgsql-admin@postgresql.org
Hi szymon,
My mistake. I chock it up to another manic monday.
Thanks!
Colin
On 8 July 2013 14:40, Colin S
Admins;
Planning to pg_upgrade some large (3TB) clusters using hard link
method. Run time for the upgrade itself takes around 5 minutes.
Nice!! Origin version 8.4 and destination version 9.1.
Unfortunately the post-upgrade analyze of the entire cluster is going
to take a minimum of 1.5 hours
