Re: Entities created in one query not available in another in extended protocol

On 11 June 2015 at 11:20, Shay Rojansky <roji(at)roji(dot)org> wrote:

> In Npgsql, the .NET driver for PostgreSQL, we've switched from simple to
> extended protocol and have received a user complaint.
>
> It appears that when we send two messages in an extended protocol (so two
> Parse/Bind/Execute followed by a single Sync), where the first one creates
> some entity (function, table), and the second one can't query that entity
> (not found). This isn't terribly important but does seem a bit odd, I
> wanted to make sure you're aware of this.
>

Sounds somewhat unlikely, but thank you for the report. Can we see a test
case?

Most commonly in such cases the first request failed and error messages
weren't checked before running second message.

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services