Andrew Dunstan wrote:
>> For Linux, perhaps some form of lsof with the +D option?
> This actually won't help. In most cases the relevant data directory has
> long disappeared out from under the rogue postmaster as part of
> buildfarm cleanup. Also, lsof is not universally available. We try to
On 01/13/2013 10:58 AM, Kevin Grittner wrote:
Andrew Dunstan wrote:
Part of the trouble with detecting rogue postmasters it might have left
lying around is that various things like to decide what port to run on,
so it's not always easy for the buildfarm to know what it should be
looking for.
Andrew Dunstan wrote:
> Part of the trouble with detecting rogue postmasters it might have left
> lying around is that various things like to decide what port to run on,
> so it's not always easy for the buildfarm to know what it should be
> looking for.
For Linux, perhaps some form of lsof wi
On 01/11/2013 01:39 PM, Tom Lane wrote:
Heikki Linnakangas writes:
There was a stray postgres instance running on the box, which I killed:
FWIW, we've seen an awful lot of persistent buildfarm failures that
seemed to be due to port conflicts with leftover postmasters. I think
the buildfarm s
Heikki Linnakangas writes:
> There was a stray postgres instance running on the box, which I killed:
FWIW, we've seen an awful lot of persistent buildfarm failures that
seemed to be due to port conflicts with leftover postmasters. I think
the buildfarm script needs to try harder to ensure that i
On 11.01.2013 18:38, Andrew Dunstan wrote:
The main feature of this release is that it does better logging of
pg_upgrade failures (which is why I hope Heikki applies it to chipmunk
right away ;-) )
Heh, ok :-)
I've upgraded it, and launched a new buildfarm run, so we'll now more in
a moment.
