| From: | Joseph Shraibman <jks(at)selectacast(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Subject: | Re: Auto-timestamp generator (attached) |
| Date: | 2001-02-09 00:30:23 |
| Message-ID: | 3A833A1F.D91ECFB8@selectacast.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
No, this is 7.0.3. Look in my pervious message where I did a version().
Tom Lane wrote:
>
> Joseph Shraibman <jks(at)selectacast(dot)net> writes:
> > It is persisting accross backend restarts, and on a newly created
> > database too. There are no views, rules, or triggers on this database.
>
> Oh? That's interesting. It might help to patch
> src/pl/plpgsql/src/pl_comp.c to show you the OID that it's unhappy about
> ... um ... waitasec. 7.0.* already *has* that patch. If you're getting
> an error message that doesn't mention an OID, you must be running a
> 7.0.0 or older plpgsql. That might not play too well with a post-7.0
> backend. Check the path that's defined for the plpgsql shlib.
>
> regards, tom lane
--
Joseph Shraibman
jks(at)selectacast(dot)net
Increase signal to noise ratio. http://www.targabot.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-02-09 00:33:16 | Re: Auto-timestamp generator (attached) |
| Previous Message | Tom Lane | 2001-02-09 00:27:57 | Re: Auto-timestamp generator (attached) |