[DOCS] Ordering of sections in chapter 22 (Localization)
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 references in sections 22.1 and 22.2 as it stands. So I'd like to flip this around --- any objections? regards, tom lane -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Ordering of sections in chapter 22 (Localization)
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 encodings. There are a lot of forward references in sections 22.1 and 22.2 as it stands. So I'd like to flip this around --- any objections? I only see these two forward references: In 22.1.1: If more than one character set can be used for a locale then the specifications can take the form language_territory.codeset. For example, fr_BE.UTF-8 represents the French language (fr) as spoken in Belgium (BE), with a UTF-8 character set encoding. In 22.2.2: Also, a collation is tied to a character set encoding (see Section 22.3). The same collation name may exist for different encodings. To me, it feels natural to discuss locales and collations first. They are a higher level feature, they affect query results and there's new syntax for collations. Encoding is just an implementation detail, you just have to set client and server encodings correctly to match your locale and the OS or application. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
[DOCS] 9.1 release notes corrections
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 Description: Binary data -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] 9.1 release notes corrections
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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Ordering of sections in chapter 22 (Localization)
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 could do with a complete rewrite, though --- it seems awkward and full of unnecessary jargon. In particular I think we could do without the phraseology about "collation derivations". But I've been staring at it for too long now to have a good idea what to do instead. regards, tom lane -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
[DOCS] Add strftime escapes to Log config
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 strftime escapes. This means that PG DBAs who are not programmers (and even some who are) end up googling for them all the time. So I would like to add the following text: Useful excape codes which are available on most platforms include: %Y = year, %m = month, %d = day of month, %H = hour, %M = minute, %a = short weekday name, and %b = short month name. -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
