Re: How to pass around collation information - Mailing list pgsql-hackers

From David Christensen
Subject Re: How to pass around collation information
Date
Msg-id 83AAD8CD-1BF0-4EE4-8963-A71726A85BFF@endpoint.com
Whole thread Raw
In response to Re: How to pass around collation information  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: How to pass around collation information  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Jun 3, 2010, at 2:43 AM, Peter Eisentraut wrote:

> On ons, 2010-06-02 at 16:56 -0400, Robert Haas wrote:
>> But in the end the only purpose of setting it on a column is to set
>> which one will be used for operations on that column.  And the user
>> might still override it for a particular query.
>
> Of course.  I'm just saying that it *can* be useful to attach a
> collation to a column definition, rather than only allowing it to be
> specified along with the sort operation.


How does collation relate to per-table/column encodings?  For that matter, are per-table/column encodings spec, and/or
somethingthat we're looking to implement down the line? 

Regards,

David
--
David Christensen
End Point Corporation
david@endpoint.com






pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Allow wal_keep_segments to keep all segments
Next
From: Heikki Linnakangas
Date:
Subject: Re: Allow wal_keep_segments to keep all segments