| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | Jakub(dot)Wartak(at)tomtom(dot)com |
| Cc: | tsunakawa(dot)takay(at)fujitsu(dot)com, osumi(dot)takamichi(at)fujitsu(dot)com, sfrost(at)snowman(dot)net, masao(dot)fujii(at)oss(dot)nttdata(dot)com, ashutosh(dot)bapat(dot)oss(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: In-placre persistance change of a relation |
| Date: | 2021-12-20 08:52:21 |
| Message-ID: | 20211220.175221.1527785299351662712.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Mon, 20 Dec 2021 17:39:27 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> At Mon, 20 Dec 2021 07:59:29 +0000, Jakub Wartak <Jakub(dot)Wartak(at)tomtom(dot)com> wrote in
> > BTW fast feedback regarding that ALTER patch (there were 4 unlogged tables):
> > # ALTER TABLE ALL IN TABLESPACE tbs1 set logged;
> > WARNING: unrecognized node type: 349
>
> lol I met a server crash. Will fix. Thanks!
That crash vanished after a recompilation for me and I don't see that
error. On my dev env node# 349 is T_ALterTableSetLoggedAllStmt, which
0002 adds. So perhaps make clean/make all would fix that.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zhihong Yu | 2021-12-20 09:21:10 | Re: simplifying foreign key/RI checks |
| Previous Message | tanghy.fnst@fujitsu.com | 2021-12-20 08:46:44 | RE: row filtering for logical replication |