Regarding pg_multixact/members folder size cleanup in postgres 9.3.6.
Dear All,
Thanks for your support and guidance.
I am using postgres 9.3.6 version and i am using multiple INSERT/UPDATE SQL
commands with explicit share lock.
I know pg_multixact/members folder contains transactions of share lock.
But these files are continuously increases.
I have checked PostgreSQL conf file and by default parameters are used in
my system.
When i have checked same behaviour in older versions of PostgreSQL, this
folder size was not increased and continuously cleanup in older versions.
Some one please let me know below points. It will really helpful to
understand postgres behavior.
1. When this folder pg_multixact/members folder size will cleanup?
2. How can i identify that at that time it will start cleanup?
3. Does it depends on some postgres config parameters? What is config
parameters and what will be value of that parameter?
4. I Want older postgres behavior in newer versions. So how to set this
behavior through postgres parameters?
Thanks in advance.
Regards,
Yogesh
On Wed, Feb 14, 2018 at 9:06 AM, Yogesh Sharma <yogeshraj95@gmail.com>
wrote:
I am using postgres 9.3.6 version and i am using multiple INSERT/UPDATE
SQL commands with explicit share lock.
[...]
4. I Want older postgres behavior in newer versions. So how to set this
behavior through postgres parameters?
You need to upgrade to 9.3.21. Also, given the issues surrounding early
9.3 releases, did this cluster/database begin its life at 9.3.6 or was
there an upgrade path to get there?
I don't know whether this is configurable but I would suspect not - your
likely issue is software bugs that have since been fixed in one or more of
the 15 releases since 9.3.6
David J.
Dear David,
Thanks for update.
I have also checked in postgres 9.3.21 and 9.5.x version. But this is same
as 9.3.6 postres version.
Regards,
Yogesh
On Wednesday, February 14, 2018, David G. Johnston <
david.g.johnston@gmail.com> wrote:
Show quoted text
On Wed, Feb 14, 2018 at 9:06 AM, Yogesh Sharma <yogeshraj95@gmail.com>
wrote:I am using postgres 9.3.6 version and i am using multiple INSERT/UPDATE
SQL commands with explicit share lock.[...]
4. I Want older postgres behavior in newer versions. So how to set this
behavior through postgres parameters?You need to upgrade to 9.3.21. Also, given the issues surrounding early
9.3 releases, did this cluster/database begin its life at 9.3.6 or was
there an upgrade path to get there?I don't know whether this is configurable but I would suspect not - your
likely issue is software bugs that have since been fixed in one or more of
the 15 releases since 9.3.6David J.
Dear David,
Show quoted text
Thanks for update.
I have also checked in postgres 9.3.21 and 9.5.x version. But this is same
as 9.3.6 postres version.
Some one please let me know below points. It will really helpful to
understand postgres behavior.
1. When this folder pg_multixact/members folder size will cleanup?
2. How can i identify that at that time it will start cleanup?
3. Does it depends on some postgres config parameters? What is config
parameters and what will be value of that parameter?
4. I Want older postgres behavior in newer versions. So how to set this
behavior through postgres parameters?Regards,
YogeshOn Wednesday, February 14, 2018, David G. Johnston <
david.g.johnston@gmail.com> wrote:On Wed, Feb 14, 2018 at 9:06 AM, Yogesh Sharma <yogeshraj95@gmail.com>
wrote:I am using postgres 9.3.6 version and i am using multiple INSERT/UPDATE
SQL commands with explicit share lock.[...]
4. I Want older postgres behavior in newer versions. So how to set this
behavior through postgres parameters?You need to upgrade to 9.3.21. Also, given the issues surrounding early
9.3 releases, did this cluster/database begin its life at 9.3.6 or was
there an upgrade path to get there?I don't know whether this is configurable but I would suspect not - your
likely issue is software bugs that have since been fixed in one or more of
the 15 releases since 9.3.6David J.