On Tue, Dec 2, 2014 at 11:54 AM, Jeff Janes wrote:
> During abort processing after getting a SIGTERM, the back end truncates
> 59288 to zero size, and unlinks all the other files (including 59288_init).
> The actual removal of 59288 is left until the checkpoint. So if you SIGTERM
> the backend, t
On Tue, Dec 2, 2014 at 7:41 AM, Robert Haas wrote:
> On Wed, Nov 26, 2014 at 7:13 PM, Jeff Janes wrote:
> > If I do a pg_ctl stop -mf, then both files go away. If I do a pg_ctl
> stop
> > -mi, then neither goes away. It is only with the /sbin/reboot that I get
> > the fatal combination of _ini
On Wed, Nov 26, 2014 at 7:13 PM, Jeff Janes wrote:
> If I do a pg_ctl stop -mf, then both files go away. If I do a pg_ctl stop
> -mi, then neither goes away. It is only with the /sbin/reboot that I get
> the fatal combination of _init being gone but the other still present.
Eh? That sounds won
On Wed, Nov 26, 2014 at 4:13 PM, Jeff Janes wrote:
> On Tue, Nov 25, 2014 at 9:30 PM, Jeff Janes wrote:
>
>> Using both 9.2.9 and 9_2_STABLE 9b468bcec15f1ea7433d4, I get a fairly
>> reproducible startup failure.
>>
>> What I was doing is restore a database from a base backup and roll it
>> forwa
On Tue, Nov 25, 2014 at 9:30 PM, Jeff Janes wrote:
> Using both 9.2.9 and 9_2_STABLE 9b468bcec15f1ea7433d4, I get a fairly
> reproducible startup failure.
>
> What I was doing is restore a database from a base backup and roll it
> forward with a recovery.conf until it completes and starts up. Th
On Thu, Nov 27, 2014 at 4:29 AM, Jeff Janes wrote:
> pg_xlogdump doesn't exist yet in 9.2 (or can I use a newer one against the
> older files?).
Not sure if pg_xlogdump would work (9.5 not for sure, 9.4 should
partially, 9.3 has better chances), but you could try this one as well
that is compatib
Hi,
On 2014-11-26 11:29:09 -0800, Jeff Janes wrote:
> On Wed, Nov 26, 2014 at 5:06 AM, Alvaro Herrera
> wrote:
>
> > Jeff Janes wrote:
> >
> > > This is what I get in the log from the attempted restart:
> > >
> > > PST LOG: database system was interrupted; last known up at 2014-11-25
> > > 15:4
On Wed, Nov 26, 2014 at 5:06 AM, Alvaro Herrera
wrote:
> Jeff Janes wrote:
>
> > This is what I get in the log from the attempted restart:
> >
> > PST LOG: database system was interrupted; last known up at 2014-11-25
> > 15:40:33 PST
> > PST LOG: database system was not properly shut down; auto
Jeff Janes wrote:
> This is what I get in the log from the attempted restart:
>
> PST LOG: database system was interrupted; last known up at 2014-11-25
> 15:40:33 PST
> PST LOG: database system was not properly shut down; automatic recovery in
> progress
> PST LOG: redo starts at 84/EF80
>
Using both 9.2.9 and 9_2_STABLE 9b468bcec15f1ea7433d4, I get a fairly
reproducible startup failure.
What I was doing is restore a database from a base backup and roll it
forward with a recovery.conf until it completes and starts up. Then I
truncate an unlogged table and start repopulating it with
10 matches
Mail list logo
