Re: Sync vs Flush - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Sync vs Flush
Date
Msg-id 856654.1593708082@sss.pgh.pa.us
Whole thread Raw
In response to Sync vs Flush  (Jaka Jančar <jaka@kubje.org>)
Responses Re: Sync vs Flush
List pgsql-hackers
=?UTF-8?B?SmFrYSBKYW7EjWFy?= <jaka@kubje.org> writes:
> For an extended query that needs to get parameter types before sending
> them, is there a difference in doing:

> Parse, Describe statement, Flush, Bind, Execute, Sync
> vs
> Parse, Describe statement, Sync, Bind, Execute, Sync

Sync is a resync point after an error, so the real question is what
you want to have happen if you get some kind of error during the Parse.
If you expect that the app wouldn't proceed with issuing Bind/Execute
then you want to do it the second way.

I suppose you could do

    Send Parse/Describe/Flush
    Read results
    If OK:
       Send Bind/Execute/Sync
    else:
       Send Sync    # needed to get back to normal state

but that doesn't sound all that convenient.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Binary support for pgoutput plugin
Next
From: Tom Lane
Date:
Subject: Re: cannot restore schema with is not distinct from on hstore since PG 9.6.8