Re: On the need for a snapshot in exec_bind_message() - Mailing list pgsql-hackers

From Daniel Wood
Subject Re: On the need for a snapshot in exec_bind_message()
Date
Msg-id 595268113.627570.1536186760616@connect.xfinity.com
Whole thread Raw
In response to Re: On the need for a snapshot in exec_bind_message()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: On the need for a snapshot in exec_bind_message()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> >     exec_bind_message()
> >         PushActiveSnapshot(GetTransactionSnapshot());
> 
> > If there were no input functions, that needed this, nor reparsing or
> > reanalyzing needed, and we knew this up front, it'd be a huge win.
> 
> Unfortunately, that's not the case, so I think trying to get rid of
> this call is a nonstarter.

Queries stop getting re-optimized after 5 times, unless better plans are to be had.  In the absence of schema changes
orchanging search path why is the snapshot needed?
 

- Dan


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: *_to_xml() should copy SPI_processed/SPI_tuptable
Next
From: Tom Lane
Date:
Subject: Re: unaccent(text) fails depending on search_path (WAS: pg_upgrade fails saying function unaccent(text) doesn't exist)