| From: | strk(at)refractions(dot)net |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, postgis-devel(at)postgis(dot)refractions(dot)net |
| Subject: | Re: caches lifetime with SQL vs PL/PGSQL procs |
| Date: | 2005-03-22 09:07:40 |
| Message-ID: | 20050322090739.GG82478@freek.keybit.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
It is embarassing for me, but I could not reproduce the bug. :(
Maybe I just ended up with a corrupted database (or I was just too tired).
Behaviour seems to be the same for both SQL and pl/pgsql functions on
a new database (and I got rid of the old one).
Sorry.
--strk;
On Thu, Mar 17, 2005 at 06:46:04PM -0500, Tom Lane wrote:
> strk(at)refractions(dot)net writes:
> > I've tried with 7.4.3 - *good* results with both SQL and PL/PGSQL
> > (actually even less that best 8.0.1: 12Mb)
>
> > I think this makes it a bug...
>
> You haven't actually provided a test case that would let someone else
> reproduce the problem ...
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-03-22 09:11:13 | Re: [HACKERS] what to do with backend flowchart |
| Previous Message | Daniel Schuchardt | 2005-03-22 08:52:04 | problem with rules - column values lost |