Re: pg_ctl stop failure

Amit

What I actually did was a 

pg_ctl stop -m f

followed by 

a pg_ctl start

then tried a 'simple' 

pg_stop stop

but this hung again so there must have been 'new' connections coming in.

Austen

-----Original Message-----
From: Amit Langote [mailto:amitlangote09@gmail.com] 
Sent: 17 May 2013 16:37
To: Birchall, Austen
Cc: pgsql-novice@postgresql.org
Subject: Re: [NOVICE] pg_ctl stop failure

On Sat, May 18, 2013 at 12:21 AM, Birchall, Austen <austen.birchall@metoffice.gov.uk> wrote:
> Thanks for this - to be honest I didn't check but if I look at it now 
> I get some transactions with
>
> | 2013-05-17 15:08:25.973161+00 | <IDLE> in transaction
> | 2013-05-17 15:08:25.745154+00 | <IDLE> in transaction
>  | 2013-05-17 14:58:24.066386+00 | <IDLE> in transaction
> | 2013-05-17 14:58:24.224678+00 | <IDLE> in transaction
>
> Which I suppose I could kill using pg_terminate_backend() although if they are rollbacked anyway?
>
>
> When I do pg_ctl start does PostgreSQL attempt to re-write them (from the WAL logs?) or as I suspect are they gone
forgood?
 
>

When you did "pg_ctl -D <data-dir> -m f stop", they were gone. I reckon you did that already, right?

Yes, since they are rolled back, they are gone for good.
What did you say about after starting the server back with "pg_ctl -D <data-dir> start"?


--
Amit Langote