From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: assertion failure w/extended query protocol |
Date: | 2012-10-19 16:41:27 |
Message-ID: | CAEYLb_UDMJV=p6qy-1duAc4GaDELG-erwx35quMkpUuzQQ4Ugg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 19 October 2012 17:19, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Rushabh Lathia of the EnterpriseDB development team and I have been
> doing some testing of the extended query protocol and have found a
> case where it causes an assertion failure. Here's how to reproduce:
>
> 1. Apply the attached patch to teach psql how to use the extended
> query protocol. Compile, install.
>
> 2. Start the modified psql and do this:
>
> \set PROTOCOL extended
> PREPARE stmt as select 1;
> CREATE TEMPORARY TABLE tmptbl AS EXECUTE stmt;
>
> The result is:
>
> TRAP: FailedAssertion("!(qry->commandType != CMD_UTILITY)", File:
> "utility.c", Line: 1516)
I'm reasonably confident that commit
9dbf2b7d75de5af38d087cbe2b1147dd0fd10f0a caused this breakage.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2012-10-19 16:56:08 | Re: First draft of snapshot snapshot building design document |
Previous Message | Robert Haas | 2012-10-19 16:38:30 | Re: First draft of snapshot snapshot building design document |