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

Re: CREATE SYNONYM ...

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
Cc: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>,Hans-J?rgen Sch?nig <postgres(at)cybertec(dot)at>,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 20:42:36
Message-ID: 20060307204236.GH58405@pervasive.com (view raw or flat)
Thread:
Lists: pgsql-patches
On Tue, Mar 07, 2006 at 12:39:55PM -0800, Stephan Szabo wrote:
> 
> On Tue, 7 Mar 2006, Jonah H. Harris wrote:
> 
> > On 3/7/06, Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> wrote:
> > >
> > > 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?
> >
> >
> > Unless synonym enablement were a configurable parameter (which wouldn't
> > really make sense), the cost would be the same whether they're used or not
> > during searching.
> 
> Right, but the response was that "using" synonyms incurred a cost and this
> should be documented.  However, if there's a cost to people not using
> synonyms there's a higher barrier to entry for the feature.

Wouldn't the cost only be incurred if you searched for something in
pg_class that wasn't there, and therefor had to fall back to pg_synonym?
(At least I'd hope it was coded this way, but I didn't look at the
patch...)
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

In response to

Responses

pgsql-patches by date

Next:From: Stephan SzaboDate: 2006-03-07 21:43:50
Subject: Re: CREATE SYNONYM ...
Previous:From: Stephan SzaboDate: 2006-03-07 20:39:55
Subject: Re: CREATE SYNONYM ...

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