[ADMIN] Problems with enums after pg_upgrade

vance Bernhard Schrader -- Bernhard Schrader System Administration InnoGames GmbH Harburger Schloßstraße 28 (Channel 4) - 21079 Hamburg - Germany Tel +49 40 7889335-53 Fax +49 40 7889335-22 Managing Directors: Hendrik Klindworth, Eike Klindworth, Michael Zillmer VAT-ID: DE264068907 Amtsgericht Ha

Re: [ADMIN] pg_database_size() and actual disk space usage

On 03/30/2012 09:20 AM, Alexander Fortin wrote: On 3/29/12 3:24 PM, Bernhard Schrader wrote: Hi, which filesystem do you use, and which kernel is running? Hi Bernhard, it's XFS on Ubuntu server 11.10, Kernel is 3.0.0-16-virtual (m1.large Ec2 instances) Ok, well with Kernel 2.6.3

Re: [ADMIN] pg_database_size() and actual disk space usage

On 03/29/2012 12:41 PM, Alexander Fortin wrote: On 3/29/12 11:41 AM, Raghavendra wrote: Can you also tell what replication is in place ? Sure thing, it's Postgresql 9.1.2, master + two replicas in streaming replication hot standby Hi, which filesystem do you use, and which kernel is runnin

Re: [ADMIN] Big difference in databasesize compared with disksize

about what could cause this behavior, please tell me. i'm getting out of ideas. Thanks a lot. regards Bernhard On 02/14/2012 02:22 PM, Bernhard Schrader wrote: Hi all, Problem: If I use SELECT pg_size_pretty(pg_database_size('dbname')) As fulldbsize; fulldbsize

[ADMIN] Big difference in databasesize compared with disksize

Hi all, Problem: If I use SELECT pg_size_pretty(pg_database_size('dbname')) As fulldbsize; fulldbsize 6455 MB (1 row) If I compare this output with /var/lib/postgresql/9.0/main/base/[DBFOLDER] I have a difference of 3 GB, which I think is not normal. To make a little bit clearer

Re: [ADMIN] Missing clogs and pg_upgrade. What to do without any clog backup?

Am Donnerstag, den 16.06.2011, 14:21 +0200 schrieb Bernhard Schrader: > Hi out there, > > i migrated some month ago our databases from 8.4 to 9.0 and now getting > errors like: > > 2011-06-12 06:25:33 CEST ERROR: could not access status of transaction > 59768467 >

[ADMIN] Missing clogs and pg_upgrade. What to do without any clog backup?

is no way around i will have to do it. thanks in advance regards Bernhard Schrader -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin

Re: [ADMIN] PG_update to 9.0.4 in ubuntu lucid 64

connections: > host all all 127.0.0.1/32 trust #md5 > host all all 172.16.0.0/21 md5 > # IPv6 local connections: > host all all ::1/128 md5 > > any idea? > > original message- > From: "Bernhard Rohrer" grayl...@sm-wg.net &

Re: [ADMIN] PG_update to 9.0.4 in ubuntu lucid 64

at some stuff is > missing in Ubuntu? > > Version BTW is 9.0.3-1 > > On 22/02/11 17:07, Bernhard Schrader wrote: > > did you installed the postgresql-9.0 contrib modules? > > > > Am Dienstag, den 22.02.2011, 14:05 + schrieb Bernhard Rohrer: > >> Hi guy

Re: [ADMIN] PG_update to 9.0.4 in ubuntu lucid 64

did you installed the postgresql-9.0 contrib modules? Am Dienstag, den 22.02.2011, 14:05 + schrieb Bernhard Rohrer: > Hi guys > > I am getting the following: > > postgres@newcollab:/usr/lib/postgresql/9.0/bin$ ./pg_upgrade > -b /usr/lib/postgresql/8.4/bin/ -B /usr/lib/postgresql/9.0/bin/ >

Re: [ADMIN] LC_COLLATE and pg_upgrade

pgrade can do his work, or is this impossible? regards Am Mittwoch, den 16.02.2011, 13:54 +0200 schrieb Peter Eisentraut: > On mån, 2011-02-14 at 14:18 +0100, Bernhard Schrader wrote: > > As far as I read right now, LC_COLLATE is a read_only variable which > > is used while

Re: [ADMIN] LC_COLLATE and pg_upgrade

Am Donnerstag, den 10.02.2011, 17:56 +0100 schrieb Bernhard Schrader: > Hi all, > > I just tried to pg_upgrade a PostgreSQL-8.4 to 9.0. > > pg_upgrade stopped with this message: > > "old and new cluster lc_collate values do not match" > > So i checked th

[ADMIN] LC_COLLATE and pg_upgrade

Hi all, I just tried to pg_upgrade a PostgreSQL-8.4 to 9.0. pg_upgrade stopped with this message: "old and new cluster lc_collate values do not match" So i checked the LC_COLLATE on 8.4 and 9.0: 8.4: postgres=# show lc_collate; lc_collate en_US.utf8 (1 row) 9.0: postgres=# show

Re: [ADMIN] pg_upgrade 8.3 to 9.0, shutdown is to slow

Am Donnerstag, den 27.01.2011, 13:12 -0500 schrieb Bruce Momjian: > Bernhard Schrader wrote: > > Am Donnerstag, den 27.01.2011, 12:09 -0500 schrieb Bruce Momjian: > > > Scott Marlowe wrote: > > > > > My initial reaction is that something is wrong with your system,

Re: [ADMIN] pg_upgrade 8.3 to 9.0, shutdown is to slow

Am Donnerstag, den 27.01.2011, 12:09 -0500 schrieb Bruce Momjian: > Scott Marlowe wrote: > > > My initial reaction is that something is wrong with your system, either > > > the I/O or the way it is being shutdown by the script. ?I would start to > > > look in the script and do some pg_ctl tests sta

Re: [ADMIN] pg_upgrade 8.3 to 9.0, shutdown is to slow

Am Donnerstag, den 27.01.2011, 09:18 -0600 schrieb Kevin Grittner: > Bernhard Schrader wrote: > > > what maybe is also interesting, if i start the database manually i > > have a huge waiting IO of 23% for a time of maybe 2-5 minutes, i > > think it is because of the fra

Re: [ADMIN] pg_upgrade 8.3 to 9.0, shutdown is to slow

that pg_ctl command manually? Is > /etc/init.d/postgresql-8.3 stop running pg_ctl or something different? > > --- > > Bernhard Schrader wrote: > > Hi all, > > > > I try to inplace migrate our

[ADMIN] pg_upgrade 8.3 to 9.0, shutdown is to slow

Hi all, I try to inplace migrate our postgresql databases from 8.3 to 9.0. So far, it worked by the testdbs I set up, it was really quick and I looked forward to migrate the live dbs. But here were some issues I didn't had in the test environment. If I start this command: """ su postgres -c "c