Re: pg_ctl stop failure - Mailing list pgsql-novice

From Amit Langote
Subject Re: pg_ctl stop failure
Date
Msg-id CA+HiwqE9kzjHuDG2Rnt6CAN=N==dVQD8mz+NGU907DD3X5ZA_Q@mail.gmail.com
Whole thread Raw
In response to Re: pg_ctl stop failure  ("Birchall, Austen" <austen.birchall@metoffice.gov.uk>)
Responses Re: pg_ctl stop failure  ("Birchall, Austen" <austen.birchall@metoffice.gov.uk>)
List pgsql-novice
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


pgsql-novice by date:

Previous
From: "Birchall, Austen"
Date:
Subject: Re: pg_ctl stop failure
Next
From: Andreas Schmitz
Date:
Subject: Re: pg_ctl stop failure