| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Sergei Kornilov <sk(at)zsrv(dot)org>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
| Subject: | Re: [HACKERS] generated columns |
| Date: | 2019-03-31 13:22:27 |
| Message-ID: | CAMkU=1xo_NW3h5-+yM=Ph_KHU09hU2mNxuOGtNuhTVZDbLgzzg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Mar 30, 2019 at 4:03 AM Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 2019-03-26 20:50, Pavel Stehule wrote:
> > It is great feature and I'll mark this feature as ready for commit
>
> Committed, thanks.
>
I can't do a same-major-version pg_upgrade across this commit, as the new
pg_dump is trying to dump a nonexistent attgenerated column from the old
database. Is that acceptable collateral damage? I thought we usually
avoided that breakage within the dev branch, but I don't know how we do it.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-03-31 14:04:22 | Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru |
| Previous Message | David Rowley | 2019-03-31 13:00:26 | Re: COPY FROM WHEN condition |