From: | Yogesh Sharma <yogeshraj95(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Regarding pg_multixact/members folder size cleanup in postgres 9.3.6. |
Date: | 2018-02-15 01:19:25 |
Message-ID: | CAEZUwCSMwvvb2tE+uTt8n0AKtv_DF93PC33d_q_QmZOv-EbW5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wed, Feb 14, 2018 at 9:06 AM, Yogesh Sharma <yogeshraj95(at)gmail(dot)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.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Yogesh Sharma | 2018-02-15 01:20:54 | Re: Regarding pg_multixact/members folder size cleanup in postgres 9.3.6. |
Previous Message | Pierre Timmermans | 2018-02-14 19:55:00 | Re: Split read/write queries between 2 servers (one master and one slave with streaming replication)? |