| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_class.relistemp |
| Date: | 2011-07-14 16:59:05 |
| Message-ID: | 16053D45-19A2-4650-8561-225B103B8643@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jul 14, 2011, at 9:55 AM, Heikki Linnakangas wrote:
> Far back. But you only need it in >= 9.1. Older versions have the pg_class.relistemp column anyway.
Yeah.
> Not sure how this helps, though. If you modify pgTAP to install that automatically in pgTAP when dealing with a new server version, you might as well modify its queries to use relispersistence = 't' directly when dealing with a new server version. It works as a manual work-around if you can't upgrade pgTAP, I guess.
Yeah, that's what I'd rather avoid. I'll probably have to modify the function that makes the call to look at the version number. Annoying, but do-able.
https://github.com/theory/pgtap/blob/master/sql/pgtap.sql.in#L5894
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-07-14 17:06:09 | Re: Need help understanding pg_locks |
| Previous Message | Kevin Grittner | 2011-07-14 16:57:03 | Re: pg_class.relistemp |