Select max(id) causes AccessExclusiveLock? - Mailing list pgsql-general

From Edson Richter
Subject Select max(id) causes AccessExclusiveLock?
Date
Msg-id BLU0-SMTP1833A6908979DF1C8928E01CF470@phx.gbl
Whole thread Raw
Responses Re: Select max(id) causes AccessExclusiveLock?  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-general by date:

Previous
From: vincent elschot
Date:
Subject: Re: Arduino SQL Connector
Next
From: Tom Lane
Date:
Subject: Re: Select max(id) causes AccessExclusiveLock?