Re: Extensions, patch v18 (merge against master, bitrot-only-fixes)

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL-Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extensions, patch v18 (merge against master, bitrot-only-fixes)
Date: 2010-12-16 17:19:17
Message-ID: B86ABB0D-3332-4A60-9952-DCD9DF3983EF@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Dec 16, 2010, at 8:19 AM, Tom Lane wrote:

> I would think that we want to establish the same policy as we have for
> dictionary files: they're assumed to be UTF-8. I don't believe there
> should be an encoding option at all. If we didn't need one for
> dictionary files, there is *surely* no reason why we have to have one
> for extension SQL files.

+1 KISS.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-12-16 17:46:43 Re: [PATCH] V3: Idle in transaction cancellation
Previous Message Tom Lane 2010-12-16 17:15:09 Re: Complier warnings on mingw gcc 4.5.0