do_sql_command(conn,"SET timezone = UTC");

do_sql_command(conn,"SET timezone ='UTC'");

if (entry->have_prep_stmt&&entry->have_error)

{

if (baserel->relid==root->parse->resultRelation&&

(root->parse->commandType==CMD_UPDATE||

</para>

</sect2>

<sect2>

<title>Cross-Version Compatibility</title>

<para>

<filename>postgres_fdw</> can be used with remote servers dating back

to <productname>PostgreSQL</> 8.3. Read-only capability is available

back to 8.1. A limitation however is that <filename>postgres_fdw</>

generally assumes that immutable built-in functions and operators are

safe to send to the remote server for execution, if they appear in a

<literal>WHERE</> clause for a foreign table. Thus, a built-in

function that was added since the remote server's release might be sent

to it for execution, resulting in <quote>function does not exist</> or

a similar error. This type of failure can be worked around by

rewriting the query, for example by embedding the foreign table

reference in a sub-<literal>SELECT</> with <literal>OFFSET 0</> as an

optimization fence, and placing the problematic function or operator

outside the sub-<literal>SELECT</>.

</para>

</sect2>

<sect2>

<title>Author</title>

<para>