| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Yogesh Sharma <yogeshraj95(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-14 16:49:56 |
| Message-ID: | CAKFQuwYa_SBA9q7Ysd3tUk1LvceywKYQK16fEN_roQ06H_493Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | DrakoRod | 2018-02-14 17:18:49 | Re: Table Partitioning: Sequence jump issue 10 in 10 with serial datatype |
| Previous Message | Yogesh Sharma | 2018-02-14 16:06:01 | Regarding pg_multixact/members folder size cleanup in postgres 9.3.6. |