Re: Add CREATE support to event triggers

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add CREATE support to event triggers
Date: 2014-02-06 02:57:58
Message-ID: CA+TgmoaJ-ZpgmFTUvzDB7QjeuX_KTna3MYGHV_wxzfW8DSemOg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 5, 2014 at 2:26 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>> Then again, why is the behavior of schema-qualifying absolutely
>> everything even desirable?
>
> Well, someone could create a collation in another schema with the same
> name as a system collation and the command would become ambiguous. For
> example, this command
> create table f (a text collate "POSIX");
> creates a column whose collation is either public."POSIX" or the system
> POSIX collation, depending on whether public appears before pg_catalog
> in search_path. Having someone create a POSIX collation in a schema
> that appears earlier than pg_catalog is pretty far-fetched, but ISTM
> that we really need to cover that scenario.

Hmm, good point. I guess we don't worry much about this with pg_dump
because we assume that we're restoring into an empty database (and if
not, the user gets to keep both pieces). You're applying a higher
standard here.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-02-06 03:31:47 Re: PoC: Partial sort
Previous Message Craig Ringer 2014-02-06 02:26:37 Re: narwhal and PGDLLIMPORT