Re: Why are default encoding conversions namespace-specific?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: ishii(at)sraoss(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Why are default encoding conversions namespace-specific?
Date: 2006-03-27 23:30:14
Message-ID: 24920.1143502214@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> Tom Lane said:
>> What does it mean to have different "default" encoding conversions in
>> different schemas? Even if this had a sensible interpretation, I don't
>> think the existing code implements it properly.

> perhaps I'm misunderstanding, but why not just resolve the namespace at the
> time the default conversion is created?

Isn't that the same thing as saying that there can only be one default
conversion across all schemas? ("Only one" for a given source and
target encoding pair, of course.) If it isn't the same, please explain
more clearly.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-03-27 23:44:46 Re: Why are default encoding conversions namespace-specific?
Previous Message Tom Lane 2006-03-27 23:02:23 Re: Why are default encoding conversions namespace-specific?