From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: reducing the overhead of frequent table locks, v4 |
Date: | 2011-07-12 17:02:01 |
Message-ID: | 1310490121.3012.274.camel@jdavis |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2011-07-12 at 07:55 -0500, Robert Haas wrote:
> I haven't been that worried about overflow of the fast path table. If
> you are locking more than 16 relations at once, you probably have at
> least 5 tables in the query, maybe more - it depends in how many
> indexes you have, of course. My assumption has been that at that
> point you're going to spend enough time planning and executing the
> query that the lock manager will no longer be a major bottleneck. Of
> course, there might be cases where that isn't so.
Yeah, I think you're right here. It's probably not much of a practical
concern.
I was slightly bothered because it seemed a little unpredictable. But it
seems very minor, and if we wanted to fix it later I think we could.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-07-12 18:11:40 | Re: Patch Review: Bugfix for XPATH() if text or attribute nodes are selected |
Previous Message | Andres Freund | 2011-07-12 16:46:22 | Deferred partial/expression unique constraints |