Thank you Tom. We will be upgrading soon.
Regards,
Granthana
On Mon, Mar 24, 2014 at 7:28 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Granthana Biswas granth...@zedo.com writes:
Version is PostgreSQL 9.1.4.
You do realize you're missing almost two years' worth of bug fixes?
The current
Sergey,
Version is PostgreSQL 9.1.4.
max_standby_archive_delay = 120s
max_standby_streaming_delay = 180s
Long running activity or idle in transactions are not there on either
master or slave as we stop all connections to both the DBs during vacuum.
Regards,
Granthana
On Fri, Mar 21, 2014 at
Granthana Biswas granth...@zedo.com writes:
Version is PostgreSQL 9.1.4.
You do realize you're missing almost two years' worth of bug fixes?
The current release in that branch is 9.1.13, and a quick look through
the git history shows quite a number of replication-related fixes.
One that seems
Hi Venkata,
No there are no other connections to the DB during vacuum.
Regards,
Granthana
On Fri, Mar 21, 2014 at 3:12 AM, Venkata Balaji Nagothi vbn...@gmail.comwrote:
On Thu, Mar 20, 2014 at 5:27 AM, Granthana Biswas granth...@zedo.comwrote:
Hello All,
Has anyone ever faced the issue
Hi Sergey,
We don't have two-phase commit prepared transactions. During vacuum, along
with this problem we are also facing streaming replication issue. Hundreds
of xlogs are in ready state in pg_xlog/archive_status. Those are being
copied manually after vacuum otherwise rsync happens very slowly
On Fri, Mar 21, 2014 at 2:46 AM, Granthana Biswas granth...@zedo.com wrote:
We don't have two-phase commit prepared transactions. During vacuum, along
with this problem we are also facing streaming replication issue. Hundreds of
xlogs are in ready state in pg_xlog/archive_status. Those are
Hello All,
Has anyone ever faced the issue of dead rows not getting removed during
vacuum even if there are no open transactions/connections?
We have been facing this during every scheduled vacuum which is done after
closing all other database connections:
119278 dead row versions cannot be
On Thu, Mar 20, 2014 at 5:27 AM, Granthana Biswas granth...@zedo.comwrote:
Hello All,
Has anyone ever faced the issue of dead rows not getting removed during
vacuum even if there are no open transactions/connections?
We have been facing this during every scheduled vacuum which is done after
On Thu, Mar 20, 2014 at 5:27 AM, Granthana Biswas granth...@zedo.com wrote:
Has anyone ever faced the issue of dead rows not getting removed during
vacuum even if there are no open transactions/connections?
What does the pg_prepared_xacts view show?
--
Kind regards,
Sergey Konoplev
PostgreSQL
On Thu, Mar 20, 2014 at 11:27 PM, Granthana Biswas granth...@zedo.com wrote:
Hello All,
Has anyone ever faced the issue of dead rows not getting removed during
vacuum even if there are no open transactions/connections?
We have been facing this during every scheduled vacuum which is done
10 matches
Mail list logo