Re: CTAS command tags - Mailing list pgsql-hackers

From Darafei "Komяpa" Praliaskouski
Subject Re: CTAS command tags
Date
Msg-id CAC8Q8t+2=qCERyRCUa_dDGs5uQM1D-S64p1YFn9_NrXz=uQCGQ@mail.gmail.com
Whole thread Raw
In response to CTAS command tags  (Vik Fearing <vik@postgresfriends.org>)
Responses Re: CTAS command tags  (Andreas Karlsson <andreas@proxel.se>)
List pgsql-hackers
Having row count right away is very useful in CTAS in analytical and GIS usage scenarios. 

пт, 22 сту 2021, 16:14 карыстальнік Vik Fearing <vik@postgresfriends.org> напісаў:
I was recently surprised by the following inconsistencies in returned
command tags for CTAS:


postgres=# create table a as select 123;
SELECT 1

postgres=# create table b as select 123 with data;
SELECT 1

postgres=# create table c as select 123 with no data;
CREATE TABLE AS


Shouldn't we make the first two tags (which are likely the same code
path; I haven't looked) the same as the third?  I can look into writing
the patch if desired.
--
Vik Fearing


pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [PATCH] Keeps tracking the uniqueness with UniqueKey
Next
From: Masahiko Sawada
Date:
Subject: Re: LogwrtResult contended spinlock