From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | M Tarkeshwar Rao <m(dot)tarkeshwar(dot)rao(at)ericsson(dot)com>, "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Getting following error in using cursor to fetch the records from a large table in c language |
Date: | 2019-10-30 17:50:28 |
Message-ID: | 1aae112c37776a169fe2e73fdaba8be84b9f3ebf.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2019-10-30 at 16:59 +0000, M Tarkeshwar Rao wrote:
> Getting following error in using cursor to fetch the records from a large table in c language.
> Can you please suggest why it is coming and what is the remedy for this.
>
> Error Details
> -----------------
> Failed to execute the sql command close:
> mycursor_4047439616_1571970686004430275FATAL: terminating connection due to conflict with recovery
> DETAIL: User query might have needed to see row versions that must be removed.
> HINT: In a moment you should be able to reconnect to the database and repeat your command.
This is not a proble with your program.
Your query is running against a standby server with "hot_standby" on,
and there are conflicts between replication and your query.
If you increase "max_standby_streaming_delay" in "postgresql.conf" on
the standby, your query will be given more time to complete.
This will, however, cause replay of the replicated changes to be delayed.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2019-10-30 22:07:32 | Re: Automatically parsing in-line composite types |
Previous Message | Francisco Olarte | 2019-10-30 17:29:12 | Re: Upgrade procedure |