Select max(id) causes AccessExclusiveLock?

From: Edson Richter <edsonrichter(at)hotmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Select max(id) causes AccessExclusiveLock?
Date: 2014-04-28 13:44:29
Message-ID: BLU0-SMTP1833A6908979DF1C8928E01CF470@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On table

create table MyTableName (
id integer not null primary key,
seqYear char(4),
seqCount integer,
...)

Where id is primary key and (seqYear, seqCount) is a unique index.
Table facts: about 40 fields, 1 million records.

When I issue a

select max(id) from MyTableName

Postgres 9.2.7 is scaling a AccessExclusiveLock and causing large delays.

Is that expected? Is there a way to avoid the AccessExclusiveLock?

Thanks,

Edson

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2014-04-28 15:01:01 Re: Select max(id) causes AccessExclusiveLock?
Previous Message vincent elschot 2014-04-28 13:27:31 Re: Arduino SQL Connector