On Thu, Mar 01, 2007 at 11:26:23 +0100,
Florian G. Pflug [EMAIL PROTECTED] wrote:
But just postponing nextval() until after the uniqueness checks
only decreases the *probability* of non-monotonic values, and
*does not* preven them. Consindert two transactions
A: begin ;
B: Begin ;
A:
Zoltan Boszormenyi wrote:
The GENERATED column is an easy of use feature
with possibly having less work, whereas the IDENTITY
column is mandatory for some applications (e.g. accounting
and billing is stricter in some countries) where you simply
cannot skip a value in the sequence, the strict
Florian G. Pflug írta:
Zoltan Boszormenyi wrote:
The GENERATED column is an easy of use feature
with possibly having less work, whereas the IDENTITY
column is mandatory for some applications (e.g. accounting
and billing is stricter in some countries) where you simply
cannot skip a value in the
Zoltan Boszormenyi írta:
Florian G. Pflug írta:
Zoltan Boszormenyi wrote:
The GENERATED column is an easy of use feature
with possibly having less work, whereas the IDENTITY
column is mandatory for some applications (e.g. accounting
and billing is stricter in some countries) where you simply
Zoltan Boszormenyi wrote:
Florian G. Pflug írta:
Zoltan Boszormenyi wrote:
The GENERATED column is an easy of use feature
with possibly having less work, whereas the IDENTITY
column is mandatory for some applications (e.g. accounting
and billing is stricter in some countries) where you simply
Florian G. Pflug írta:
Yes, of course you can prevent gaps by just filling them
with garbage/invalid records of whatever. But I don't see
why this is usefull - either you want, say, your invoice
number to be continuous because it's required by law - or
you don't. But if the law required your
Zoltan Boszormenyi írta:
The cost I am thinking now is an extra heap_update()
after heap_insert() without generating the identity value
and inserting index tuples to indexes that doesn't
contain the identity column.
And as far as I tested the current state, there is no cost
if you don't use
Zoltan Boszormenyi [EMAIL PROTECTED] writes:
However, I get warning messages like:
WARNING: detected write past chunk end in ExecutorState 0xaaff68
How can I prevent them?
Find the memory-clobbering bug in your patch.
regards, tom lane
---(end
Tom Lane írta:
Zoltan Boszormenyi [EMAIL PROTECTED] writes:
However, I get warning messages like:
WARNING: detected write past chunk end in ExecutorState 0xaaff68
How can I prevent them?
Find the memory-clobbering bug in your patch.
regards, tom lane
Hi,
I would like to be able to harden the conditions
of generating IDENTITY columns so the
events below run in this order:
- assign values for regular columns (with or without DEFAULT)
- NOT NULL checks on regular columns
- CHECK constraints whose expression contains only regular columns
-
Zoltan Boszormenyi [EMAIL PROTECTED] writes:
Would it be acceptable?
No, because you can't create index entries when you haven't yet got the
TID for the heap tuple. What do you propose doing, insert a dummy index
entry and then go back to fill it in later? Aside from approximately
doubling the
Hi,
Tom Lane írta:
Zoltan Boszormenyi [EMAIL PROTECTED] writes:
Would it be acceptable?
No, because you can't create index entries when you haven't yet got the
TID for the heap tuple. What do you propose doing, insert a dummy index
entry and then go back to fill it in later? Aside
12 matches
Mail list logo
