| From: | David Christensen <david(at)endpoint(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How to pass around collation information |
| Date: | 2010-06-03 12:30:56 |
| Message-ID: | 83AAD8CD-1BF0-4EE4-8963-A71726A85BFF@endpoint.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 something that we're looking to implement down the line?
Regards,
David
--
David Christensen
End Point Corporation
david(at)endpoint(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-06-03 12:31:30 | Re: Allow wal_keep_segments to keep all segments |
| Previous Message | Bruce Momjian | 2010-06-03 12:15:22 | Re: Allow wal_keep_segments to keep all segments |