pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Zhihong Yu <zyu@yugabyte.com>
Cc: Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Subject: Re: Dumping/restoring fails on inherited generated column
Date: Tue, 4 May 2021 12:27:03 +0200
Message-ID: <7d27c190-c065-6946-c9d4-0d3542959ee6@enterprisedb.com> (raw)
In-Reply-To: <ac35da1c-e746-ea19-bfc3-84819a4e907d@enterprisedb.com>
References: <15830.1575468847@sss.pgh.pa.us>
	<CA+fd4k4cHKUmEyHiPHx0QL3T-DXAP8O1CP-hUvo1WX6RwNC=tA@mail.gmail.com>
	<3f272982-0e0d-17a1-3fb6-fedc74197676@2ndquadrant.com>
	<c9848634-76c1-3c21-fc19-f1b7eebb640f@2ndquadrant.com>
	<3169466.1594841366@sss.pgh.pa.us>
	<CA+fd4k4fck6xzsF8mPWeVSZFBLtiA2cQxrPqBaYcoZGc+hZ=JQ@mail.gmail.com>
	<CA+fd4k6pLzrZDQsdsxcS06AwGRf1DgwOw84sFq9oXNw+83nB1g@mail.gmail.com>
	<e87e2efe-c820-c0d3-f7a0-0789beb78ff1@2ndquadrant.com>
	<CAD21AoCfgYKJo3cEhoUr4cKWxmSxi_gdHQDmOJ5XKC-dDc4yBw@mail.gmail.com>
	<e8e3f666-9050-1029-42cf-d0ecfdb8902e@2ndquadrant.com>
	<0f57d5e9-4112-1ba8-64d8-c02062c1e95d@postgrespro.ru>
	<41888c80-e5bd-f9e5-75dc-fb377113168c@2ndquadrant.com>
	<2808494.1611938475@sss.pgh.pa.us>
	<22de27f6-7096-8d96-4619-7b882932ca25@2ndquadrant.com>
	<CALNJ-vS1PtJBk3v73Bq3dM9J46=P3jAcXOLjjtZ7w2fPYsg-7A@mail.gmail.com>
	<0dbc982e-fbb3-911e-eb80-130494664940@2ndquadrant.com>
	<ac35da1c-e746-ea19-bfc3-84819a4e907d@enterprisedb.com>

On 26.04.21 14:10, Peter Eisentraut wrote:
> On 05.02.21 15:18, Peter Eisentraut wrote:
>> Anyway, I figured out how to take account of generation expressions 
>> with different column orders.  I used the same approach that we use 
>> for check constraints.  The attached patch is good to go from my 
>> perspective.
> 
> Dusting this off ... this patch should go into the next minor releases. 
> The attached patch is for master but backpatches without manual 
> intervention to PG13 and PG12.

committed





view thread (37+ messages)

Message-ID: <7d27c190-c065-6946-c9d4-0d3542959ee6@enterprisedb.com>
Permalink:  ../7d27c190-c065-6946-c9d4-0d3542959ee6@enterprisedb.com/
Also on:    postgresql.org/message-id/7d27c190-c065-6946-c9d4-0d3542959ee6@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@enterprisedb.com, pgsql-hackers@lists.postgresql.org, tgl@sss.pgh.pa.us, sawada.mshk@gmail.com, zyu@yugabyte.com, masahiko.sawada@2ndquadrant.com
  Subject: Re: Dumping/restoring fails on inherited generated column
  In-Reply-To: <7d27c190-c065-6946-c9d4-0d3542959ee6@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox