Re: Ending EXPLAIN ANALYZE early (was Re: That EXPLAIN ANALYZE patch still needs work)

From: "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Ending EXPLAIN ANALYZE early (was Re: That EXPLAIN ANALYZE patch still needs work)
Date: 2006-06-09 07:35:22
Message-ID: E1539E0ED7043848906A8FF995BDA5790116B8C0@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> This bothers me a bit, because in
> fact the effects if any of the tested query would have been
> rolled back. Not sure we have any choice though. If we
> expose the error then we'll have problems with clients not
> showing the EXPLAIN results.

I think we should leave it in top level, throw the error and fix the
clients.
As I understood, the idea was, that it only does that if you
press ^C or query timeout. In this case current clients would also
not show the plan.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nis Jorgensen 2006-06-09 08:12:21 Re: Fabian Pascal and RDBMS deficiencies in fully implementing
Previous Message Zeugswetter Andreas DCP SD 2006-06-09 07:14:57 Re: More on inheritance and foreign keys