Skip site navigation (1) Skip section navigation (2)

Re: PQexecPrepared() behavior

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PQexecPrepared() behavior
Date: 2009-08-30 16:09:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
> Strange thing is, it seems PQexecPrepared() sends B(bind), Describe,
> Execute and Sync at once without checking the result of Bind
> message. Is this leagal from a point of view of the frontend/backend
> protocol?

Yes.  If we failed to do this then every query would involve multiple
network round-trips, which would be catastrophic for performance.
The Sync message is used to make error recovery well-defined.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-08-30 16:24:15
Subject: Re: drop tablespace error: invalid argument
Previous:From: Greg StarkDate: 2009-08-30 15:10:49
Subject: Re: clang's static checker report.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group