Simon Riggs wrote:
> On Fri, 2007-12-14 at 10:47 +0100, Adriaan van Os wrote:
> > Simon Riggs wrote:
> > > Sounds interesting but needs to be on pgsql-hackers, please.
> >
> > I posted a message to pgsql-hackers three times but it gets stalled (and
> > the owner of the list
> > doesn't reply).
On Fri, 2007-12-14 at 10:47 +0100, Adriaan van Os wrote:
> Simon Riggs wrote:
> > On Mon, 2007-12-10 at 12:31 +0100, hubert depesz lubaczewski wrote:
> >> On Sun, Dec 09, 2007 at 03:32:17PM +, Simon Riggs wrote:
> >>> ALTER SEQUENCE blah INCREMENT BY val;
> >> this has the sideeffect that all c
"NikhilS" <[EMAIL PROTECTED]> writes:
> Coincidently, I very briefly discussed (offline) about supporting
> expressions while doing loads using COPY FROM with Heikki a while back. From
> the above mail exchanges, it does appear that adding this kind of
> functionality will be useful while doing bu
On Mon, 2007-12-10 at 12:31 +0100, hubert depesz lubaczewski wrote:
> On Sun, Dec 09, 2007 at 03:32:17PM +, Simon Riggs wrote:
> > ALTER SEQUENCE blah INCREMENT BY val;
>
> this has the sideeffect that all concurrent nextvals() will also
> increment by val, which is not always acceptable.
So
Hi,
> > Right, I want to use it with a bulk operation, say importing a million
> records
> > with COPY. Calling nextval one million times looks to me like an
> enormous waste
> > of resources. Suppose, you are on an ADSL line: it will cost one million
> times
> > the ping time of the ADSL line (sa
On Sun, Dec 09, 2007 at 03:32:17PM +, Simon Riggs wrote:
> ALTER SEQUENCE blah INCREMENT BY val;
this has the sideeffect that all concurrent nextvals() will also
increment by val, which is not always acceptable.
depesz
--
quicksil1er: "postgres is excellent, but like any DB it requires a
hi
"Adriaan van Os" <[EMAIL PROTECTED]> writes:
> Right, I want to use it with a bulk operation, say importing a million records
> with COPY. Calling nextval one million times looks to me like an enormous
> waste
> of resources. Suppose, you are on an ADSL line: it will cost one million times
> the
"Michael Glaesemann" <[EMAIL PROTECTED]> writes:
> On Dec 9, 2007, at 9:24 , Adriaan van Os wrote:
>
>> 3. nextval doesn't have an optional "increase" parameter (the increase is
>> always one).
>
> Not true. Please read the documentation at
>
> http://www.postgresql.org/docs/8.2/static/sql-create
On Dec 9, 2007, at 9:24 , Adriaan van Os wrote:
1. LOCK TABLE doesn't work on a sequence
2. nextval will happily ignore ISOLATION LEVEL SERIALIZABLE of
concurrent
transactions
Nor should it. Sequences are *by design* non-lockable and non-blocking.
http://www.postgresql.org/docs/faqs.FAQ
On Sun, 2007-12-09 at 09:24 +, Adriaan van Os wrote:
> The following bug has been logged online:
>
> Bug reference: 3811
> Logged by: Adriaan van Os
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2.5
> Operating system: Mac OS X 10.5
> Description:Getti
The following bug has been logged online:
Bug reference: 3811
Logged by: Adriaan van Os
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Mac OS X 10.5
Description:Getting multiple values from a sequence generator
Details:
The following ha
11 matches
Mail list logo
