I have applied the attached patch to document this issue.
---
On Fri, Jun 15, 2012 at 11:05:30AM -0700, Josh Berkus wrote:
> Folks,
>
> Way it is now:
>
> ===
>
> max_locks_per_transaction (integer)
>
> T
Excerpts from Josh Berkus's message of jue jun 21 18:53:06 -0400 2012:
>
> > I don't know, because I can't see what's changed if you don't send a
> > diff. It would be fine if you sent a diff between plain text, to
> > illustrate what you mean, even if it's not the actual source code.
>
> Odd;
> I don't know, because I can't see what's changed if you don't send a
> diff. It would be fine if you sent a diff between plain text, to
> illustrate what you mean, even if it's not the actual source code.
Odd; nobody else seems to have had trouble understanding my post.
--
Josh Berkus
Postgr
On ons, 2012-06-20 at 14:47 -0700, Josh Berkus wrote:
> > This would be easier to process if you had sent a diff.
>
> Do you agree with the changes? I can send a diff. I personally find
> SGML impossible to read, though, so I never propose changes that way.
I don't know, because I can't see wha
> This would be easier to process if you had sent a diff.
Do you agree with the changes? I can send a diff. I personally find
SGML impossible to read, though, so I never propose changes that way.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-docs mailing l
On fre, 2012-06-15 at 11:05 -0700, Josh Berkus wrote:
> Folks,
>
> Way it is now:
> The way it should be:
This would be easier to process if you had sent a diff.
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mai
On Fri, 2012-06-15 at 12:37 -0700, Josh Berkus wrote:
> Hmmm. I think we should also say "partitioning", as well as
> "inheritance". Maybe:
>
> "Extensive use of table inheritance, such as for tables with many
> partitions, may require raising this setting."
http://www.postgresql.org/docs/9.2/s
On 6/15/12 12:25 PM, Jeff Davis wrote:
> On Fri, 2012-06-15 at 11:05 -0700, Josh Berkus wrote:
>> The default, 64, has historically proven sufficient for most databases,
>> but you might need to raise this value if you have clients that touch
>> many different tables in a single transaction. Datab
On Fri, 2012-06-15 at 11:05 -0700, Josh Berkus wrote:
> The default, 64, has historically proven sufficient for most databases,
> but you might need to raise this value if you have clients that touch
> many different tables in a single transaction. Databases with several
> tables with many partiti
Folks,
Way it is now:
===
max_locks_per_transaction (integer)
The shared lock table tracks locks on max_locks_per_transaction *
(max_connections + max_prepared_transactions) objects (e.g., tables);
hence, no more than this many distinct objects can be locked at any one
time. Thi
10 matches
Mail list logo
