Skip site navigation (1) Skip section navigation (2)

Re: CREATE SYNONYM ...

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Hans-Jürgen Schönig <postgres(at)cybertec(dot)at>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Michael Glaesemann <grzm(at)myrealbox(dot)com>,pgsql-patches(at)postgresql(dot)org, eg(at)cybertec(dot)at
Subject: Re: CREATE SYNONYM ...
Date: 2006-03-07 17:55:33
Message-ID: 20060307091535.J41035@megazone.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-patches
On Tue, 7 Mar 2006, [ISO-8859-1] Hans-Jrgen Schnig wrote:

> > The semantics of namespace search seem wrong; I would think that a
> > synonym in schema A should mask a table in schema B if A precedes B
> > on the search path, but this doesn't work that way.
>
> good point.
> any other opionions here?

I'd generally agree with Tom's assessment for this.  That seems to be the
most reasonable behavior to me.

> > I'm also not very happy about adding an additional catalog search to
> > function and table lookup, which are already quite expensive enough.
>
> oracle documentation also states that using synonyms will add overhead.
> people will know that and this should be part of the documentation.
> however, i think - the performance impact when using this feature is
> less painful for the customer than any kind of problem related to legacy
> or duplicate code - people using features like that have to pay the
> price for that.

I'd personally be more interested in what the impact is on people not
using synonyms. How free is any search for synonyms if you aren't using
the feature?

In response to

Responses

pgsql-patches by date

Next:From: Jonah H. HarrisDate: 2006-03-07 19:57:47
Subject: Re: CREATE SYNONYM ...
Previous:From: Jonah H. HarrisDate: 2006-03-07 17:30:17
Subject: Re: CREATE SYNONYM ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group