From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Markus <t.markus@proventis.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: problems with access into system catalogs
Date: Thu, 26 Jul 2012 10:45:51 -0400
Message-ID: <20495.1343313951@sss.pgh.pa.us> (raw)
In-Reply-To: <5011260F.2060105@proventis.net>
References: <5010F555.9020209@proventis.net>
<5010FEF2.3050901@ringerc.id.au>
<5011025B.7050003@proventis.net>
<50110E39.1040601@ringerc.id.au>
<5011260F.2060105@proventis.net>
Thomas Markus <t.markus@proventis.net> writes:
> a rollback prepared on these does the job
If you aren't intentionally using prepared transactions, it's a good
idea to disable them by setting max_prepared_transactions to zero
(DB restart required). That prevents you from accidentally shooting
yourself in the foot like this.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, t.markus@proventis.net
Subject: Re: problems with access into system catalogs
In-Reply-To: <20495.1343313951@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox