Re: prokind column (was Re: [HACKERS] SQL procedures) - Mailing list pgsql-hackers

From John Naylor
Subject Re: prokind column (was Re: [HACKERS] SQL procedures)
Date
Msg-id CAJVSVGXbZwZ1mFF8w+85X=SDRWo2VMTcd6rxX+1RMa3fPqwGnQ@mail.gmail.com
Whole thread Raw
In response to Re: prokind column (was Re: [HACKERS] SQL procedures)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2/25/18, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> We need a plan for when/how to apply this, along with the proposed
> bootstrap data conversion patch, which obviously conflicts with it
> significantly.

The bulk changes in the bootstrap data patch are scripted rather than
patched, so the prokind patch will pose little in the way of
conflicts. I can't verify this just yet since Peter's second patch
doesn't apply for me against c4ba1bee68ab. Also, as of version 7 my
patch left out default values and human-readable oids, since I wanted
to get the new generated headers reviewed and up to project standards
first. Since I'll likely have to adjust the patches for those features
anyway, there's plenty of room for me to adjust to the changes to
pg_proc.h as well.

> My thought here is that the data conversion patch is going to break
> basically every pending patch that touches src/include/catalog/,
> so we ought to apply it at a point where that list of patches is short
> and there's lots of time for people to redo them.  Hence, end of the
> dev cycle is the right time.

I agree.

-John Naylor


pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: [HACKERS] PATCH: multivariate histograms and MCV lists
Next
From: Craig Ringer
Date:
Subject: Re: handling of heap rewrites in logical decoding