Radek, Zdenek, and Heikki had an extended discussion here at PGDay.it on
collation support. I was volunteered to be the note-taker (!). Here is the
plan we came up with:
Firstly, the ANSI standard makes collations into schema-qualified names which
pretty much forces us to have the collation
On Fri, 2008-10-17 at 16:47 -0400, Merlin Moncure wrote:
On Fri, Oct 17, 2008 at 10:38 AM, Simon Riggs [EMAIL PROTECTED] wrote:
First integrated patch for Hot Standby, allowing queries to be executed
while in recovery mode.
The patch tests successfully with the enclosed files:
*
On Tue, 2008-10-07 at 10:35 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
On Tue, 2008-10-07 at 10:05 -0400, Robert Haas wrote:
3. The patch introduces a slight weirdness: if you create two FKs on the
same column at the same time you end up with two constraints with
Normally I would lurk on this list for a month or two before I considered
posting, but I saw a note on collation and thought some of you might be
interested in my experience implementing collation for the ANTs Data Server.
In ADS, we treated the collation internally as part of the type for string
On Sat, Oct 18, 2008 at 07:41:12AM +0100, Gregory Stark wrote:
The ANSI standard syntax where the COLLATION keyword can follow just about any
string value in an expression and then bubbles up the expression until an
operation needs to pick a collation seemed very weird to us. Hooking that into
Here is a patch that allows the new SQL:2008 syntax (also used by IBM)
ALTER TABLE tab ALTER COLUMN col SET DATA TYPE typ
alongside our current syntax
ALTER TABLE tab ALTER COLUMN col TYPE typ
I verified that we implement a superset what the standard says. (Of
course, the standard
On Sat, Oct 18, 2008 at 4:11 AM, Simon Riggs [EMAIL PROTECTED] wrote:
On Fri, 2008-10-17 at 16:47 -0400, Merlin Moncure wrote:
On Fri, Oct 17, 2008 at 10:38 AM, Simon Riggs [EMAIL PROTECTED] wrote:
First integrated patch for Hot Standby, allowing queries to be executed
while in recovery
Martijn van Oosterhout [EMAIL PROTECTED] writes:
It's quite straightforward. Every expression has a collation, the COLLATE
keyword just overrides it. And the collation is a parameter of the
operators/functions that want to use it. Implementation is also
straightforward: add expr :: expr
I just spent a couple of days trying to figure out why I couldn't start
two servers on the same port, even though I was configuring separate
listen_address values. I kept gettting errors about shmget failing with
could not create shared memory segment: Invalid argument.
I finally noticed that
Tom Lane [EMAIL PROTECTED] writes:
It's fairly irritating to think that a string-specific option is going
to become part of the fundamental type system --- it makes no sense to
distinguish different collations for numeric for instance
Actually I thought of that generality as an advantage.
Eric Haszlakiewicz [EMAIL PROTECTED] writes:
I just spent a couple of days trying to figure out why I couldn't start
two servers on the same port, even though I was configuring separate
listen_address values.
That's already documented not to work, and not for any hidden
implementation reason:
Tom Lane wrote:
Eric Haszlakiewicz [EMAIL PROTECTED] writes:
I just spent a couple of days trying to figure out why I couldn't start
two servers on the same port, even though I was configuring separate
listen_address values.
That's already documented not to work, and not for any
Andrew Dunstan [EMAIL PROTECTED] writes:
Tom Lane wrote:
That's already documented not to work, and not for any hidden
implementation reason: you'd have a conflict on the Unix-domain socket
name.
unless you use a different socket directory.
Hmm ... but the OP didn't mention any such thing.
On Sat, Oct 18, 2008 at 11:28:41AM -0400, Tom Lane wrote:
It's fairly irritating to think that a string-specific option is going
to become part of the fundamental type system --- it makes no sense to
distinguish different collations for numeric for instance (and in fact
I would want to see the
On Fri, Oct 17, 2008 at 7:54 PM, Nathan Boley [EMAIL PROTECTED] wrote:
I'm still working my way around the math, but copulas sound better
than anything else I've been playing with.
I think the easiest way to think of them is, in 2-D finite spaces,
they are just a plot of the order statistics
Someone at the PostgreSQL West conference last weekend expressed an
interest in a Lisp procedural language. The only two Lisp environments
I've found so far that aren't GPL are Steel Bank Common Lisp (MIT,
http://sbcl.sourceforge.net) and XLispStat (BSD,
From what I remember with tinkering with Lisp a while back, SBCL and CMUCL
are the big free implementations. I remember something about GCL being
non-standard. Either of those should make lisp hackers happy.
2008/10/18 M. Edward (Ed) Borasky [EMAIL PROTECTED]
Someone at the PostgreSQL West
On Sat, 2008-10-18 at 20:43 -0400, Nikolas Everett wrote:
From what I remember with tinkering with Lisp a while back, SBCL and
CMUCL are the big free implementations. I remember something about
GCL being non-standard. Either of those should make lisp hackers
happy.
GCL (and Clisp) are both
M. Edward (Ed) Borasky wrote:
On Sat, 2008-10-18 at 20:43 -0400, Nikolas Everett wrote:
From what I remember with tinkering with Lisp a while back, SBCL and
CMUCL are the big free implementations. I remember something about
GCL being non-standard. Either of those should make lisp hackers
M. Edward (Ed) Borasky [EMAIL PROTECTED] writes:
GCL (and Clisp) are both reasonable implementations of Common Lisp.
However, they are both GPL, which I think is an issue for PostgreSQL
community members.
Well, it would be an issue if we wanted to distribute PL/Lisp as part of
the core; but I
20 matches
Mail list logo
