On 2015-02-11 19:54, Jan Stary wrote:
> On Feb 11 14:49:17, h...@barrera.io wrote:
> > Hi,
> >
> > I upgraded to -snapshot today, and did all the proper postgresql upgrade:
> > pg_dump, moved the old db out the the way, re-init'd, started, and
import.
> >
> > The thing is, upon receiving connections, postgres dies horribly. The log
is
> > just this following iterating over and over:
> >
> >   WARNING:  terminating connection because of crash of another server
process
> >   DETAIL:  The postmaster has commanded this server process to roll back
the
> >   current transaction and exit, because another server process exited
> > abnormally
> >   and possibly corrupted shared memory.
> >   HINT:  In a moment you should be able to reconnect to the database and
> > repeat
> >   your command.
> >   LOG:  all server processes terminated; reinitializing
> >   LOG:  database system was interrupted; last known up at 2015-02-11
17:01:00
> > GMT
> >   LOG:  database system was not properly shut down; automatic recovery in
> >   progress
> >   LOG:  record with zero length at 0/1696370
> >   LOG:  redo is not required
> >   LOG:  database system is ready to accept connections
> >   LOG:  autovacuum launcher started
> >   LOG:  server process (PID 9444) was terminated by signal 6: Abort trap
> >   LOG:  terminating any other active server processes
> >
> > After much frustration (even building -current), I deleted all of it,
> > uninstall, built 9.3.4 using the old ports recipe, installed - same
issue!
> >
> > It's clearly not an upgrade issue, because deleting all the data files
and
> > going back to 9.3 has the same issue.
>
> Have you stopped the DB server before performing the upgrade?
> Are you sure (pgrep -fl post) that there is no other server process
> around?
>
>       Jan
>

Yes, I did. I also did this when installing the version I built from ports
(which I also tried with no change).

I actually did the entire process a few times, with -snapshots, -current and
installing from packages.

All exhibited the same behaviour, so I'm starting to suspect the issue is not
postgres per se.

> > Has anyone else has this issue, or similar issues with
-snapshot/-current?
> > Can
> > someone else confirm postgres9.4 work fine on the latest -snapshot? (the
> > confirmation would be helpful to reafirm that it's not an issue with some
> > dependency or library).
> >
> > Thanks,
> >
> > --
> > Hugo Osvaldo Barrera
> > A: Because we read from top to bottom, left to right.
> > Q: Why should I start my reply below the quoted text?
> >
> > [demime 1.01d removed an attachment of type application/pgp-signature]

--
Hugo Osvaldo Barrera
A: Because we read from top to bottom, left to right.
Q: Why should I start my reply below the quoted text?

[demime 1.01d removed an attachment of type application/pgp-signature]

Reply via email to