Re: Extensions, patch v18 (merge against master, bitrot-only-fixes) - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Extensions, patch v18 (merge against master, bitrot-only-fixes)
Date
Msg-id B86ABB0D-3332-4A60-9952-DCD9DF3983EF@kineticode.com
Whole thread Raw
In response to Re: Extensions, patch v18 (merge against master, bitrot-only-fixes)  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Complier warnings on mingw gcc 4.5.0
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] V3: Idle in transaction cancellation