Re: Another thought about search_path semantics

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Another thought about search_path semantics
Date: 2014-04-04 18:02:56
Message-ID: 533EF3D0.6040508@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 04/04/2014 01:47 PM, Andres Freund wrote:
> I wonder if we could extend the search path syntax to specify whether a
> schema should be used for creation of objects or not. Sounds somewhat
> nasty, but I don't really have a better idea :(. Something like
> search_patch=public,!pg_catalog.

No, if we're fixing this, then we should have a separate
"creation_target_schema" GUC. The fact that the only way to designate
creation target schema was to put it at the start of the search path has
*always* been a problem, since 7.3.

Non-atomic data sucks. ;-b

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-04-04 18:05:11 Re: Another thought about search_path semantics
Previous Message Tom Lane 2014-04-04 17:58:53 Re: Another thought about search_path semantics