Sorry, late reaction.
Yeah, me too.
Done! thanks.
Regards,
Hiroshi Saito
- Original Message -
From: "Dave Page"
I'm inclined to accept this for beta 3. Although it seems like a new
feature, the inability to set PGCLIENTENCODING where it may be
required could be considered a bug.
I'm inclined to accept this for beta 3. Although it seems like a new
feature, the inability to set PGCLIENTENCODING where it may be
required could be considered a bug.
Thoughts?
On Mon, Jun 7, 2010 at 4:43 PM, Hiroshi Saito wrote:
> Ooops, this:-)
>
> - Original Message - From: "Dave Pag
Ooops, this:-)
- Original Message -
From: "Dave Page"
Show us the patch man!!
:-)
On Mon, Jun 7, 2010 at 4:28 PM, Hiroshi Saito wrote:
Hi.
I need setenv for plugins. Because, there must not be client_encoding in
Japan.
It does not function now.
The following specifications are
Show us the patch man!!
:-)
On Mon, Jun 7, 2010 at 4:28 PM, Hiroshi Saito wrote:
> Hi.
>
> I need setenv for plugins. Because, there must not be client_encoding in
> Japan.
> It does not function now.
> The following specifications are considered. Environment -
> VARIABLE=VALUE[,VARIABLE=VALUE]
Hi.
I need setenv for plugins. Because, there must not be client_encoding in Japan.
It does not function now.
The following specifications are considered.
Environment - VARIABLE=VALUE[,VARIABLE=VALUE]
example)
Environment=PGCLIENTENCODING=SJIS,OTHERS_ENV=VAL
It is important to have a functio
