From: | "Higuchi, Daisuke" <higuchi(dot)daisuke(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | 'Michael Meskes' <meskes(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: [Bug Fix] ECPG: could not use some CREATE TABLE AS syntax |
Date: | 2019-02-18 09:19:29 |
Message-ID: | 1803D792815FC24D871C00D17AE95905DB49C1@g01jpexmbkw24 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi, Meskes-san
> Yes, I fully understand that. However, in doing so you accept
> statements that the backend later on rejects. The sole reason for
> the big ecpg grammar is to prevent those cases whenever possible.
Ok, I agree with you.
> > I also want to hear your opinion. I will change my opinion flexibly.
> I agree that this the way to go.
I updated and attached the patch. As I show in previous post, this version is that "IF NOT EXISTS" keyword and variable for "WITH NO DATA" are added to ecpg.trailer.
Regards,
Daisuke, Higuchi
Attachment | Content-Type | Size |
---|---|---|
FIX_ECPG_CREATE_TABLE_AS_v2.patch | application/octet-stream | 11.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2019-02-18 09:19:40 | Re: propagating replica identity to partitions |
Previous Message | Jakub Glapa | 2019-02-18 09:11:10 | Re: dsa_allocate() faliure |