From: | Darafei "Komяpa" Praliaskouski <me(at)komzpa(dot)net> |
---|---|
To: | Vik Fearing <vik(at)postgresfriends(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: CTAS command tags |
Date: | 2021-01-22 13:19:06 |
Message-ID: | CAC8Q8t+2=qCERyRCUa_dDGs5uQM1D-S64p1YFn9_NrXz=uQCGQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)postgresfriends(dot)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
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2021-01-22 13:23:46 | Re: LogwrtResult contended spinlock |
Previous Message | Masahiko Sawada | 2021-01-22 13:14:40 | Re: [PATCH] Keeps tracking the uniqueness with UniqueKey |