| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Дмитрий Иванов <firstdismay(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_dump insert column GENERATED |
| Date: | 2021-11-21 16:24:09 |
| Message-ID: | 3443243.1637511849@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?UTF-8?B?0JTQvNC40YLRgNC40Lkg0JjQstCw0L3QvtCy?= <firstdismay(at)gmail(dot)com> writes:
>> So did you do an ALTER TABLE ... GENERATED ALWAYS AS on bpg.object in
>> the Postgres 12 version of the database?
> I think you're right, I added later.
Hmm, that's suggestive, but I tried making a table that way and still did
not see any pg_dump misbehavior.
It might be useful to see the results of this query on the v12 server:
select attname, attgenerated from pg_attribute
where attrelid = 'bpd.object'::regclass and attnum > 0;
We should see attgenerated = 's' for the generated column, but
maybe we don't?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-11-21 16:27:10 | Re: insert column monetary type ver 2 |
| Previous Message | vincent.veyron@libremen.org | 2021-11-21 15:46:48 | Re: insert column monetary type ver 2 |