Re: [HACKERS] Unique index: update error

2006-09-18 Thread Simon Riggs
On Fri, 2006-09-15 at 09:16 +0800, Golden Liu wrote: > this problem I'm sorry but I don't see any problem. Why would you want to issue that kind of SQL statement? Assuming you really do, why not just DELETE/re-INSERT ? -- Simon Riggs EnterpriseDB http://www.enterprisedb.com

Re: [HACKERS] 8.2 beta blockers

2006-09-18 Thread Lukas Kahwe Smith
Peter Eisentraut wrote: Am Montag, 18. September 2006 09:20 schrieb Lukas Kahwe Smith: This just reminds me, are there plans to take into account multibyte server encodings inside the client quote function? Huh? Ah, I just checked the libpq docs and there seems to be a PQescapeStringConn. N

Re: [HACKERS] Opinion about macro for the uuid datatype.

2006-09-18 Thread Peter Eisentraut
Am Montag, 18. September 2006 13:50 schrieb Gevik Babakhani: > It was My question was, "Could you do this using a domain?". The possible answers to that are "Yes" and "No", neither of which appears below, nor does "domain". > Gevik Babakhani <[EMAIL PROTECTED]> writes: > > I was wondering if I

Re: [HACKERS] 8.2 beta blockers

2006-09-18 Thread Christopher Browne
Quoth [EMAIL PROTECTED] (Tom Lane): > Christopher Browne <[EMAIL PROTECTED]> writes: >> A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Tom Lane) >> wrote: >>> I see the following items standing between us and putting out 8.2beta1: >>> * AIX linking issues > >> This has to do with t

Re: [HACKERS] Opinion about macro for the uuid datatype.

2006-09-18 Thread Gevik Babakhani
It was Gevik Babakhani <[EMAIL PROTECTED]> writes: > I was wondering if I should go ahead and add a macro datatype like the > SERIAL, only this time for the uuid. This assumes a fact not in evidence, which is that we're going to accept a uuid-generation function as part of core. AFAIK the only r

Re: [HACKERS] Opinion about macro for the uuid datatype.

2006-09-18 Thread Peter Eisentraut
Am Montag, 18. September 2006 13:28 schrieb Gevik Babakhani: > > Could you do this using a domain? > > Tom had a very good point about this. And that point was? -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)---

Re: [HACKERS] Reducing data type space usage

2006-09-18 Thread Hannu Krosing
Ühel kenal päeval, R, 2006-09-15 kell 19:34, kirjutas Tom Lane: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Oh, OK, I had high byte meaning no header, but clear is better, so > > 0001 is 0x01, and is "". But I see now that bytea does > > store nulls, so yea, we would be better usi

Re: guc comment changes (was Re: [HACKERS] Getting a move on for 8.2 beta)

2006-09-18 Thread Joachim Wieland
On Mon, Sep 18, 2006 at 01:13:45PM +0200, Peter Eisentraut wrote: > Joachim Wieland is in the process of reworking the original feature patch > (resetting commented out parameters) in a much more compact form. But it > turns out that there are a couple of very tricky situations involving custom

Re: [HACKERS] Opinion about macro for the uuid datatype.

2006-09-18 Thread Gevik Babakhani
On Mon, 2006-09-18 at 13:20 +0200, Peter Eisentraut wrote: > Am Sonntag, 17. September 2006 01:47 schrieb Gevik Babakhani: > > The development of the uuid datatype is yet in progress... > > I was wondering if I should go ahead and add a macro datatype like the > > SERIAL, only this time for the uui

Re: [HACKERS] 8.2 beta blockers

2006-09-18 Thread Peter Eisentraut
Am Montag, 18. September 2006 01:38 schrieb Tom Lane: > * Set client encoding based on OS environment - Peter E. This is not an item for 8.2 in my mind. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 4: H

Re: [HACKERS] 8.2 beta blockers

2006-09-18 Thread Peter Eisentraut
Am Montag, 18. September 2006 09:20 schrieb Lukas Kahwe Smith: > This just reminds me, are there plans to take into account multibyte > server encodings inside the client quote function? Huh? -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadca

Re: [HACKERS] Opinion about macro for the uuid datatype.

2006-09-18 Thread Peter Eisentraut
Am Sonntag, 17. September 2006 01:47 schrieb Gevik Babakhani: > The development of the uuid datatype is yet in progress... > I was wondering if I should go ahead and add a macro datatype like the > SERIAL, only this time for the uuid. Could you do this using a domain? -- Peter Eisentraut http://

Re: guc comment changes (was Re: [HACKERS] Getting a move on for 8.2 beta)

2006-09-18 Thread Peter Eisentraut
Am Freitag, 15. September 2006 20:32 schrieb Tom Lane: > I've finally taken a close look at this patch, and I don't like it any > more than Peter does. The refactoring might or might not be good at its > core, but as presented it is horrid. Joachim Wieland is in the process of reworking the origi

Re: [HACKERS] [PATCHES] Patch for UUID datatype (beta)

2006-09-18 Thread Gevik Babakhani
On Mon, 2006-09-18 at 11:11 +0200, Harald Armin Massa wrote: > Gevik, > >uniqueness is never a guaranteed. that is according to the RFC docs. > > >uniqueness is never a guaranteed in the sense that there is a tiny > >chance someone of the other side of the planet might generate the > same > >guid

Re: [HACKERS] UUID/GUID discussion leading to request for hexstring bytea?

2006-09-18 Thread Gevik Babakhani
> Magnitude comparison on the GUID as a whole makes no > sense to me. I agree. Any kind of comparison except equality has no meaning for the GUID. (And this is discussed before) I rather have the option to sort and group for the sake of consistency and compatibility. --

Re: [HACKERS] -HEAD planner issue wrt hash_joins on dbt3 ?

2006-09-18 Thread Matteo Beccati
Hi, Tom Lane wrote: Hmm ... pattern_sel already applies the operator directly to the most_common_vals, but in this situation those aren't common enough to help much. With such an extensive histogram it is awfully tempting to assume that the histogram members are a representative sample, and tak

Re: [HACKERS] UUID/GUID discussion leading to request for hexstring bytea?

2006-09-18 Thread Thomas Hallgren
Gevik Babakhani wrote: LIKE could come handy if someone wants to abuse the uuid datatype to store MD5 hash values. However I am not going to implement it if there is no need for that (assuming it will pass the acceptance test) Perhaps providing LIKE just to encourage abuse is not such a good

Re: [HACKERS] UUID/GUID discussion leading to request for hexstring bytea?

2006-09-18 Thread Gevik Babakhani
LIKE could come handy if someone wants to abuse the uuid datatype to store MD5 hash values. However I am not going to implement it if there is no need for that (assuming it will pass the acceptance test) On Mon, 2006-09-18 at 10:06 +0200, Thomas Hallgren wrote: > Gevik Babakhani wrote: > > To my

Re: [HACKERS] UUID/GUID discussion leading to request for hexstring bytea?

2006-09-18 Thread Thomas Hallgren
Gevik Babakhani wrote: To my opinion GUIDs type need to provide the following in the database. 1. GUID type must accept the correct string format(s), with of without extra '-' 2. GUID type must internally be stored as small as possible. 3. GUID type must be comparable with == , != , LIKE and (N

Re: [HACKERS] TODO item: GUID

2006-09-18 Thread Thomas Hallgren
[EMAIL PROTECTED] wrote: ... I *like* sorting by time, as it allows the UUID to be used similar to sequence, leaving older, lesser accessed UUIDs in the past. and don't forget, an automatic timestamp of when a record is created might be useful for other purposes. Regards, Thomas Hallgren -

Re: [HACKERS] Release notes

2006-09-18 Thread Teodor Sigaev
I see two entries: * Improve subtransaction performance (Alvaro, Itagaki Takahiro, Tom) * Improve sub-transaction performance (Itagaki Takahiro) Aren't they the same? Markup: New operators for array-subset comparisons (<@, @>, &&) -- Teodor Sigaev E-ma

Re: [HACKERS] 8.2 beta blockers

2006-09-18 Thread Lukas Kahwe Smith
Tom Lane wrote: I see the following items standing between us and putting out 8.2beta1: * Set client encoding based on OS environment - Peter E. I'm not sure whether Peter is intending to complete this item for 8.2 or not, but if it's to be done it ought to be done before we start beta. This

<    1   2