| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: some more error location support |
| Date: | 2018-08-30 06:36:36 |
| Message-ID: | 12a05f66-4bb1-da6d-4b7a-9ede47066c86@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 29/08/2018 16:39, Fabien COELHO wrote:
>
>>> The majority rule (34 make & 22 free) suggest that it is more often use
>>> than not. I'd suggest to stick to that for consistency & homogeneity.
>>
>> But it's consistently not used in DDL command implementations, only in
>> normal query parsing.
>
> I try to avoid complicated (context-sensitive) rules when I can, esp as
> some functions may be called from DDL and DML.
>
> But fine with me.
Committed 0001 and 0002, keeping 0003 for future research, as discussed.
Thanks.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-08-30 06:39:22 | Re: Removing useless \. at the end of copy in pgbench |
| Previous Message | Simon Riggs | 2018-08-30 06:28:17 | Re: "Write amplification" is made worse by "getting tired" while inserting into nbtree secondary indexes (Was: Why B-Tree suffix truncation matters) |