Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread Niels Kristian Schjødt
Solved it - thanks! Den 10/06/2013 kl. 20.24 skrev Jeff Janes : > On Mon, Jun 10, 2013 at 11:02 AM, Niels Kristian Schjødt > wrote: > Okay, cool > > You mean that I should do the following right?: > > 1. Stop slave server > > > At this point, you don't have a slave server. Not a usable one

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread Niels Kristian Schjødt
Thanks, > No, you shouldn't do that yet without first having correctly functioning > archiving back in place. After setting archive_command=true and reloading > the server, you have to wait a while for the "bad" WAL files to get > pseudo-archived and cleared from the system. How do I know whe

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread Jeff Janes
On Mon, Jun 10, 2013 at 11:02 AM, Niels Kristian Schjødt < nielskrist...@autouncle.com> wrote: > Okay, cool > > You mean that I should do the following right?: > > 1. Stop slave server > At this point, you don't have a slave server. Not a usable one, anyway. If you used to have a hot-standby s

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread Niels Kristian Schjødt
Okay, cool You mean that I should do the following right?: 1. Stop slave server 2. set archive_command = 'true' in postgresql.conf on the master server 3. restart master server 4. run psql -c "SELECT pg_start_backup('label', true)" on master 5. run rsync -av --exclude postmaster.pid --exclude pg_

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread Matheus de Oliveira
On Mon, Jun 10, 2013 at 12:35 PM, Niels Kristian Schjødt < nielskrist...@autouncle.com> wrote: > > Den 10/06/2013 kl. 16.36 skrev bricklen : > > On Mon, Jun 10, 2013 at 4:29 AM, Niels Kristian Schjødt < > nielskrist...@autouncle.com> wrote: > >> >> 2013-06-10 11:21:45 GMT FATAL: could not connect

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread Jeff Janes
On Mon, Jun 10, 2013 at 8:35 AM, Niels Kristian Schjødt < nielskrist...@autouncle.com> wrote: > > WARNING: pg_stop_backup still waiting for all required WAL segments to be > archived (1920 seconds elapsed) > HINT: Check that your archive_command is executing properly. > pg_stop_backup can be ca

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread bricklen
On Mon, Jun 10, 2013 at 8:51 AM, bricklen wrote: > > On Mon, Jun 10, 2013 at 8:35 AM, Niels Kristian Schjødt < > nielskrist...@autouncle.com> wrote: > >> I can't seem to figure out which steps I need to do, to get the standby >> server wiped and get it started as a streaming replication again fro

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread Niels Kristian Schjødt
Den 10/06/2013 kl. 17.51 skrev bricklen : > > On Mon, Jun 10, 2013 at 8:35 AM, Niels Kristian Schjødt > wrote: > I can't seem to figure out which steps I need to do, to get the standby > server wiped and get it started as a streaming replication again from > scratch. I tried to follow the st

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread bricklen
On Mon, Jun 10, 2013 at 8:35 AM, Niels Kristian Schjødt < nielskrist...@autouncle.com> wrote: > I can't seem to figure out which steps I need to do, to get the standby > server wiped and get it started as a streaming replication again from > scratch. I tried to follow the steps, from step 6, in he

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread Niels Kristian Schjødt
Den 10/06/2013 kl. 16.36 skrev bricklen : > On Mon, Jun 10, 2013 at 4:29 AM, Niels Kristian Schjødt > wrote: > > 2013-06-10 11:21:45 GMT FATAL: could not connect to the primary server: > could not connect to server: No route to host > Is the server running on host "192.168.0.

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread bricklen
On Mon, Jun 10, 2013 at 4:29 AM, Niels Kristian Schjødt < nielskrist...@autouncle.com> wrote: > > 2013-06-10 11:21:45 GMT FATAL: could not connect to the primary server: > could not connect to server: No route to host > Is the server running on host "192.168.0.4" and accepting >

Re: [PERFORM] Not same plan between static and prepared query

2013-06-10 Thread Ghislain ROUVIGNAC
Hello Amit, Thank you for your help. You are right, it work fine with PostgreSQL 9.2. *Ghislain ROUVIGNAC* 2013/6/6 Amit Kapila > > On Thursday, June 06, 2013 1:56 PM Ghislain ROUVIGNAC wrote: > > Hello, > > > > We have a strange issue related to a prepared statement. > > > > We have two

Re: [PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread Dinesh Kumar
> Hi, My pg_xlog dir has been growing rapidly the last 4 days, and my disk > is now almost full (1000Gb) even though the database is only 50Gb. I have a > streaming replication server running, and in the log of the slave it says: > > cp: cannot stat `/var/lib/postgresql/9.2/wals/00020E1B000

[PERFORM] URGENT issue: pg-xlog growing on master!

2013-06-10 Thread Niels Kristian Schjødt
Hi, My pg_xlog dir has been growing rapidly the last 4 days, and my disk is now almost full (1000Gb) even though the database is only 50Gb. I have a streaming replication server running, and in the log of the slave it says: cp: cannot stat `/var/lib/postgresql/9.2/wals/00020E1B00A9':

Re: [PERFORM] Not same plan between static and prepared query

2013-06-10 Thread Amit Kapila
On Sunday, June 09, 2013 8:45 PM Yuri Levinsky wrote: > Amit, > It's very strength for me to hear that PostgreSQL generate execution > plan for prepared statements during execution, I always was thinking > that the purpose of the prepared statement is to eliminate such > behavior. It doesn't alwa