Search Postgresql Archives

Re: Best approach for a "gap-less" sequence

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: PostgreSQL General ML <pgsql-general@xxxxxxxxxxxxxx>
Subject: Re: Best approach for a "gap-less" sequence
From: AgentM <agentm@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 17 Aug 2006 11:25:04 -0400
In-reply-to: <878xlnil8g.fsf@xxxxxxxxx>
References: <87u04ic0g2.fsf@xxxxxxxx> <44E0D827.1040004@xxxxxxxxxxxxxxxx> <1155589148.29917.18.camel@xxxxxxxxxxxxxxxxxxxxxxx> <200608141446.18198.aklaver@xxxxxxxxxxx> <20060816175921.GG355@xxxxxxxxxxx> <44E376F6.7010802@xxxxxxxxxxxxxxxx> <878xlnil8g.fsf@xxxxxxxxx>

Just in case no one else has brought it up- 8.1+ supports 2PC andsavepoints, so one alternative would be to run your standardinsertion operations in a prepared transaction or savepoint block. Ifyou get so far as being able to prepare the transaction/complete thesavepoint block, you should be able to snag a sequence id and commiteverything.

-M

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Best approach for a "gap-less" sequence
  - From: Jorge Godoy
- Re: Best approach for a "gap-less" sequence
  - From: Berend Tober
- Re: Best approach for a "gap-less" sequence
  - From: Brad Nicholson
- Re: Best approach for a "gap-less" sequence
  - From: Adrian Klaver
- Re: Best approach for a "gap-less" sequence
  - From: elein
- Re: Best approach for a "gap-less" sequence
  - From: Berend Tober
- Re: Best approach for a "gap-less" sequence
  - From: Jorge Godoy

Prev by Date: Re: COLLATE
Next by Date: PostgreSQL getting slower over time, restart of service cures the problem
Previous by thread: Re: Best approach for a "gap-less" sequence
Next by thread: Re: Best approach for a "gap-less" sequence
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]