Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Hackers > Re: Re: [COMMIT...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 3 of 3 Topic 9263 of 10389
Post > Topic >>

Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing

by Andreas.Zeugswetter@[EMAIL PROTECTED] ("Zeugswetter Andreas OSB S Apr 28, 2008 at 10:54 AM

> I don't understand this if it's calling option 2 the monolithic
> implementation. I was intending that the values be permanent tokens if
> you like, so that ZERO rewriting would be required for any types of
> modification. So I don't see where locking comes in. I don't want
> rewriting either.

I think you are not considering existing btree indexes here
(for the reordering case) ?

So +1 on a solution that has naturally sorting keys (e.g. your 1).=20

Andreas

--=20
Sent via pgsql-hackers mailing list (pgsql-hackers@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
 




 3 Posts in Topic:
Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated
pgsql@[EMAIL PROTECTED]   2008-04-26 03:31:37 
Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated
tgl@[EMAIL PROTECTED] (T  2008-04-25 18:28:57 
Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated
Andreas.Zeugswetter@[EMAI  2008-04-28 10:54:06 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Sat Oct 11 6:14:27 CDT 2008.