Re: current is broken

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: current is broken
Date: 2000-09-13 05:02:51
Message-ID: 6182.968821371@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
>> Ooops. I guess libpq needs to supply a copy of this function?

> Simply copying the function won't work since the way to know what
> encoding is used for this session is different between backend and
> frontend.

Good point --- in fact, the encoding itself might be different between
the backend and frontend. That seems to imply that "truncate to
NAMEDATALEN bytes" could yield different results in the frontend than
what the backend would get.

> Even better idea would be creating a new function that returns the
> actual rule name (after being shorten) from given view name. I don't
> think it's a good idea to have codes to get an actual rule name in two
> separate places.

Given the above point about encoding differences, I think we *must*
do the truncation in the backend ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-09-13 05:31:51 RE: current is broken
Previous Message Tatsuo Ishii 2000-09-13 04:56:46 Re: current is broken