I'm wondering why chapter 22 discusses locales (and now collations)
before encodings. ISTM the logical order is the reverse, because
encodings can be explained without reference to locales, but it's very
difficult to cover locales without touching on encodings. There are a
lot of forward referenc
On 20.03.2011 09:06, Tom Lane wrote:
I'm wondering why chapter 22 discusses locales (and now collations)
before encodings. ISTM the logical order is the reverse, because
encodings can be explained without reference to locales, but it's very
difficult to cover locales without touching on encoding
Hi,
I attach a patch to address various errata in the PostgreSQL 9.1 release notes.
Thanks
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
9.1_release_notes_fixes.patch
On Sun, Mar 20, 2011 at 12:57, Thom Brown wrote:
> Hi,
>
> I attach a patch to address various errata in the PostgreSQL 9.1 release
> notes.
Applied, thanks!
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-docs mailing list (pgsql-doc
Heikki Linnakangas writes:
> On 20.03.2011 09:06, Tom Lane wrote:
>> I'm wondering why chapter 22 discusses locales (and now collations)
>> before encodings.
> To me, it feels natural to discuss locales and collations first.
OK, I left that alone.
I can't escape the feeling that section 22.2 co
All,
This page:
http://www.postgresql.org/docs/8.3/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHERE
has the following text:
The value is treated as a strftime pattern, so %-escapes can be used to
specify time-varying file names.
However, nowhere in our docs do we list sample str
