| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgstattuple change using SRF |
| Date: | 2002-08-21 06:11:28 |
| Message-ID: | 20020821.151128.66326626.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > I'm going to change contrib/pgstattuple so that it returns a tuple
> > rather than a NOTICE using new SRF interface. I believe this way is
> > much more convenient for users. Any objection?
>
> Sure. I like the way Joe did show_all() better than the way Neil
> did lock_status() --- I'm in the middle of getting rid of zero
> type OIDs throughout the system, and so I'm not happy with anything
> that re-introduces them, even if it's only transient during initdb.
> Other than that minor point, go for it...
I think pgstattuple() never uses OPAQUE...
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2002-08-21 06:13:22 | Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in |
| Previous Message | Tatsuo Ishii | 2002-08-21 06:06:12 | Re: How to disable encoding validation during database restore |