On Mon, Aug 14, 2017 at 11:58 PM, Michael Paquier
wrote:
> 1) It is easy to add a wait event and...
> 2) It is easy to not update its documentation.
> 3) the documentation tables get easily broken.
>
> As I have participated in the situation present now, I propose to
> write a patch to make the ma
On Mon, Aug 14, 2017 at 11:58 PM, Michael Paquier
wrote:
> As $subject has been touched on two threads recently
> (https://www.postgresql.org/message-id/CAB7nPqTbHLcHFn6m11tfpwAdgz8BmnBza2jjN9AK=sdx_kb...@mail.gmail.com
> and
> https://www.postgresql.org/message-id/20170808213537.wkmmagf2a6i3hjyi
On Tue, Sep 26, 2017 at 4:28 PM, Michael Paquier
wrote:
> Gathering a set of examples on wiki page with some rough
> analysis I think would be a good start.
I don't seem to have privs to create wiki pages; can someone else make
a page where we can begin to gather things like this?
Does https://w
On Sun, Oct 1, 2017 at 8:10 AM, Tom Lane wrote:
>
> configure --with-extra-version=whateveryouwant
I see that this build option has been around since 9.4; is anyone
using it to mark patched production builds? EnterpriseDB or
2ndQuadrant? How about the cloud providers?
-Jeremy
--
http://about.
On Wed, Oct 11, 2017 at 1:19 AM, Craig Ringer wrote:
> We started using it for BDR, but unfortunately too much software
> explodes spectacularly when you use it, due to simplistic/buggy
> version parsing.
Since 10.0 will break most of that software anyway, maybe this is a
good time to revisit the
Hi,
whenever pg calls my input function, the type modifier parameter is
ALWAYS (-1). If I specify a type modifier like
SELECT 'Hello World!'::my_string_type(MODIFIER1,MODIFIER2);
then pg:
1. calls the my_string_type-typmod_in function, and gets the correct result
2. calls the my_string_type-i
