Re: [PATCH] SET search_path += octopus - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PATCH] SET search_path += octopus
Date
Msg-id 20201029012930.6cupprd2wjqmwshd@alap3.anarazel.de
Whole thread Raw
In response to Re: [PATCH] SET search_path += octopus  (Abhijit Menon-Sen <ams@toroid.org>)
Responses Re: [PATCH] SET search_path += octopus  (Abhijit Menon-Sen <ams@toroid.org>)
List pgsql-hackers
Hi,

On 2020-10-21 10:05:40 +0530, Abhijit Menon-Sen wrote:
> > It seems to me that appending and incrementing using the same syntax
> > is a) confusing b) will be a limitation before long.
> 
> I understand (a), but what sort of limitation do you foresee in (b)?
> 
> Do you think both features should be implemented, but with a different
> syntax, or are you saying incrementing should not be implemented now?

I'm not sure, it just seems likely to me. Consider e.g. user defined
GUCs, where the type isn't yet known - just having type based dispatch
won't work well there.

For lists it also seems like you'd sometimes want prepend and sometimes
append.

After pondering this in the back of my mind for a while, I think my gut
feeling about this still is that it's not worth implementing something
that doesn't work in postgresql.conf. The likelihood of ending up with
something that makes it hard to to eventually implement proper
postgresql.conf seems high.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Tatsuro Yamada
Date:
Subject: Re: list of extended statistics on psql
Next
From: Tatsuro Yamada
Date:
Subject: Re: list of extended statistics on psql