From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | "Birchall, Austen" <austen(dot)birchall(at)metoffice(dot)gov(dot)uk> |
Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: pg_ctl stop failure |
Date: | 2013-05-17 15:37:22 |
Message-ID: | CA+HiwqE9kzjHuDG2Rnt6CAN=N==dVQD8mz+NGU907DD3X5ZA_Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Sat, May 18, 2013 at 12:21 AM, Birchall, Austen
<austen(dot)birchall(at)metoffice(dot)gov(dot)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 for good?
>
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
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Schmitz | 2013-05-18 09:15:38 | Re: pg_ctl stop failure |
Previous Message | Birchall, Austen | 2013-05-17 15:21:06 | Re: pg_ctl stop failure |