Re: Problem with dumping bloom extension

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problem with dumping bloom extension
Date: 2016-06-08 14:45:49
Message-ID: 20160608144549.GV21416@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Noah Misch (noah(at)leadboat(dot)com) wrote:
> Yep, pretty much that. CLOSE_WAIT is for performance defects, race
> conditions, and other defects where a successful fix is difficult to verify
> beyond reasonable doubt. Other things can move directly to "resolved". I
> don't mind if practice diverges from that intent, and I don't really process
> the two sections differently.

Ok, thanks for the clarification. I've updated the entries which I had
accordingly.

Thanks again!

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-06-08 14:47:43 Re: Rename max_parallel_degree?
Previous Message Robert Haas 2016-06-08 14:44:26 Re: hstore: add hstore_length function