[GENERAL] Streaming replication with automatic failover?

2012-01-04 Thread Saurabh
Hi all, After a discussion (https://groups.google.com/group/pgsql.performance/ browse_thread/thread/98ff8dd854be0b10/a26f49b4f4c60012? hl=en#a26f49b4f4c60012), we have decide to stick with streaming replication. But now the question is how to implement the automatic failover either using some appl

[GENERAL] Postgresql 9.1 logging

2012-01-04 Thread Birta Levente
Hi all I use postgresql 9.1.2 on centos 6.2 and I want to use pgfouine, but in my log file appear #011, #015 ... characters and the pgfouine can't handle it. Can I configure the server or rsyslog to log without these characters or I need filter separately? thanks Levi the log section from m

Re: [GENERAL] Postgresql 9.1 logging

2012-01-04 Thread Andreas Kretschmer
Birta Levente wrote: > Hi all > > I use postgresql 9.1.2 on centos 6.2 and I want to use pgfouine, but in > my log file appear #011, #015 ... characters and the pgfouine can't > handle it. > Can I configure the server or rsyslog to log without these characters or > I need filter separately?

[GENERAL] help... lost database after upgrade from 9.0 to 9.1

2012-01-04 Thread Bruno Boettcher
Hello! just made a stupid move... upgraded a working system and without checking if the backup was ok so i end up with a debian system having upgraded to 9,1 without converting the database, and a scrambled backup which is totally unusable i tried to start the old tree with pg_ctlcl

[GENERAL] help... lost database after upgrade from 9.0 to 9.1

2012-01-04 Thread bboett
Hello! just made a stupid move... upgraded a working system and without checking if the b

[GENERAL] delayed post: Subject: help... lost database after upgrade from 9.0 to 9.1

2012-01-04 Thread bboett
Hello, got a delaying message for my post because i visibly send from the wrong machine, tryed (hopefully) from the right one to resend it -- ciao bboett == bbo...@adlp.org http://inforezo.u-strasbg.fr/~bboett/ =

[GENERAL] help... lost database after upgrade from 9.0 to 9.1

2012-01-04 Thread bboett
Hello! just made a stupid move... upgraded a working system and without checking if the b

Re: [GENERAL] help... lost database after upgrade from 9.0 to 9.1

2012-01-04 Thread Adrian Klaver
On Wednesday, January 04, 2012 6:50:25 am Bruno Boettcher wrote: > Hello! > > just made a stupid move... upgraded a working system and without > checking if the backup was ok > > so i end up with a debian system having upgraded to 9,1 without > converting the database, and a scrambled bac

[GENERAL] PGAdmin3 for 9.1 and CentOS-5_x86_64

2012-01-04 Thread James B. Byrne
I cannot seem to find a copy of pgadmin3 built for 9.1 on the x86_64 platform for the CentOS-5 (RHEL5) distro. I can find a pgadmin3 v1.14.1 rpm package for rhel6.x86_64 but none for rhel5.x86_64. I sent a message off to the maintainer last week but with the holidays no doubt it is sitting in h

Re: [GENERAL] help... lost database after upgrade from 9.0 to 9.1

2012-01-04 Thread Adrian Klaver
On Wednesday, January 04, 2012 9:46:42 am you wrote: > On Wed, Jan 04, 2012 at 07:41:32AM -0800, Adrian Klaver wrote: > Hello! > > > Define scrambled backup. I am CCing list so more eyes can see this. > > well disks on both side had block loss, without me noticing > so the backups were

Re: [GENERAL] Duplicated entries are not ignored even if a "do instead nothing" rule is added.

2012-01-04 Thread Alban Hertroys
You accidentally clicked "Reply" instead of "Reply-all" ;) On 4 Jan 2012, at 3:03, 邓尧 wrote: >> On Tue, Jan 3, 2012 at 3:42 PM, Alban Hertroys wrote: >> On 3 Jan 2012, at 5:20, 邓尧 wrote: >> >> > Hi, >> > >> > I'm new to pgsql, I need the do something like the "INSERT IGNORE" in >> > mysql. Aft

Re: [GENERAL] Duplicated entries are not ignored even if a "do instead nothing" rule is added.

2012-01-04 Thread Daniele Varrazzo
On Wed, Jan 4, 2012 at 8:09 PM, Alban Hertroys wrote: > On 4 Jan 2012, at 3:03, 邓尧 wrote: >> True, I don't need transactions, neither do I want them, but psycopg2 create >> transactions for me automatically :-( > > Well, if psycopg didn't, Postgres would wrap each statement in a transaction >