Re: [PATCH] SET search_path += octopus

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Abhijit Menon-Sen <ams(at)toroid(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] SET search_path += octopus
Date: 2020-10-20 18:16:12
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Given that this is just SQL level, I don't see why we'd need a special
> type of language here. You can just use DO etc.

I'd make that point against the whole proposal. There's nothing here that
can't be done with current_setting() + set_config(). I'm pretty dubious
about layering extra functionality into such a fundamental utility command
as SET; and the fact that we've gone twenty-odd years without similar
previous proposals doesn't speak well for it being really useful.

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Isaac Morland 2020-10-20 18:16:48 Re: [PATCH] SET search_path += octopus
Previous Message Andres Freund 2020-10-20 17:53:04 Re: [PATCH] SET search_path += octopus