RE: current is broken - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject RE: current is broken
Date
Msg-id 20000913194136N.t-ishii@sra.co.jp
Whole thread Raw
In response to RE: current is broken  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Responses RE: current is broken
List pgsql-hackers
> > 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 ...
> >
> 
> I agree with Tatsuo.
> However we already have relkind for views.
> Why must we rely on rulename to implement isViewRule()
> in the first place ? 

Oh, I forgot about that.

BTW, does anybody know about the status of pg_dump? It seems tons of
features have been added, but I wonder if all of them are going to
appear in 7.1.  Especially now it seems to have an ability to dump
Blobs, but the flag (-b) to enable the feature has been disabled. Why?
--
Tatsuo Ishii


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: PL/pgSQL does not accept none ASCII identifiers
Next
From: Denis Perchine
Date:
Subject: Fwd: Problems inserting data