Postgres Pro
Downloads
Home   >   mailing lists

Re: Problem with dumping bloom extension - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Problem with dumping bloom extension
Date
Msg-id 20160607203845.GG21416@tamriel.snowman.net
Whole thread Raw
In response to Re: Problem with dumping bloom extension  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Tree view 
* Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote:
> On 6/7/16 11:16 AM, Stephen Frost wrote:
> >Moved to CLOSE_WAIT.
>
> Could you add an explanation on the wiki page about what this section means?

I understood it to simply be a step on the way to being resolved- that
is, everything goes through CLOSE_WAIT for some period of time and then
is moved to resolved when it's clear that the consensus is that it's
closed.

That doesn't appear to be the consensus on the meaning though, and I
didn't add it, so I'm not the one to update the wiki page to explain it.

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Parallel pg_dump's error reporting doesn't work worth squat
Next
From: Jean-Pierre Pelletier
Date:
Subject: Should phraseto_tsquery('simple', 'blue blue') @@ to_tsvector('simple', 'blue') be true ?