From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Florin Irion <irionr(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Reserve prefixes for loaded libraries proposal |
Date: | 2021-10-21 06:02:44 |
Message-ID: | YXEChET5Y5Re35pZ@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 30, 2021 at 11:54:04PM +0200, Florin Irion wrote:
> We could also help users get a warning if they set a parameter with the
> `SET`
> command. I've seen many cases where users make typos and break things badly,
> check the following example:
>
> ```
> postgres=# BEGIN;
> BEGIN
> postgres=*# SET plpgsql.no_such_setting = false;
> SET
> postgres=*# -- do critical queries taking into account that
> plpgsql.no_such_setting is false;
> postgres=*# COMMIT;
> COMMIT
> ```
Could you give a more concrete example here? What kind of critical
work are you talking about here when using prefixes? Please note that
I am not against the idea of improving the user experience in this
area as that's inconsistent, as you say.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2021-10-21 06:04:39 | Re: [Bug] Logical Replication failing if the DateStyle is different in Publisher & Subscriber |
Previous Message | Greg Nancarrow | 2021-10-21 05:57:48 | Re: Data is copied twice when specifying both child and parent table in publication |