| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rod Taylor <rbt(at)rbt(dot)ca> |
| Cc: | Michael Paesold <mpaesold(at)gmx(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Backend crash (long) |
| Date: | 2002-09-18 15:15:27 |
| Message-ID: | 17981.1032362127@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Rod Taylor <rbt(at)rbt(dot)ca> writes:
> On Wed, 2002-09-18 at 11:03, Tom Lane wrote:
>> "Michael Paesold" <mpaesold(at)gmx(dot)at> writes:
> I have written a test function, that will create a sequence and a table,
> than insert one million rows into the table, analyze the table and create an
> index on one of the columns.
>>
>> You can't run ANALYZE inside a function. In CVS tip there's a check to
>> prevent the VACUUM variant of this problem, but I'm not sure if it
>> handles the ANALYZE variant (yet).
> ANALYZE in 7.3 works fine in a transaction, so it shouldn't it be able
> to work in a function as well?
Possibly it's okay in 7.3; I have a note to look at that, but haven't
done it yet. I think REINDEX has the same problem btw ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB SD | 2002-09-18 16:01:05 | Re: Proposal for resolving casting issues |
| Previous Message | Tom Lane | 2002-09-18 15:12:19 | Re: The notorious to_char bug |