Hi everyone.
Previous message needed some rethinking and was sent like that by my mistake.
From what I figured out now: pgAdmin is using Unicode as the client
setting no matter what the database is set to. The database was set
to win1252. A comment in the settings file states that
client_enco
Hi ADMIN,
Pls exclude me from the mailing list.
Regards,
Subash
-
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
Hi
For those having the same problem .
1. You need to change the codepage in shell/command prompt to 1252
(chcp 1252) and set the window to use truetype font to have it
displayed correctly.
2. Execute "set client_encoding='win1252';" to have the translation
working properly from the shell. H
All,
have a cluster that hit the wrap-around issue.
We are trying to run the backend vacuum as describe in the manual to
clear up the problem.
I not sure how I should be interrupting the messages I'm receiving
from the vacuum command.
Here is the approach I take so far (note pg 8.1.4 Linux
Warren Little <[EMAIL PROTECTED]> writes:
> I not sure how I should be interrupting the messages I'm receiving
> from the vacuum command.
Just do the vacuums. It's deliberately very noisy about impending
wraparound shutdown, to make sure you notice before it's too late.
8.2.3
I was hoping to not have to support client certs. I want
encryption and to verify the server, but no to verify the client.
Does this work and I've got the config wrong?
I get ssl connections if I add in the .postgresql/postgresql.crt+key.
Results seem similar to this report:
http://archiv
Ray Stell <[EMAIL PROTECTED]> writes:
> I was hoping to not have to support client certs. I want
> encryption and to verify the server, but no to verify the client.
> Does this work and I've got the config wrong?
Maybe I misunderstand what you want --- doesn't leaving out the
server's root.crt fi
Hello,
I understand that this is probably outside the realm of Postgres itself, so
if no one has a really good definite answer, that's fine. Still, I thought
I'd fish for information and see if anyone else has run into this problem.
I've already made a bug report to the DBD::Pg folks.
The proble
Hi Everybody,
What is the difference between creating a rule and a trigger?
Regards
skarthi
_
i'm making a difference. Make every IM count for the cause of your choice. Join
Now.
http://clk.atdmt.com/MSN/go/msnnkwme00800
Karthikeyan Sundaram wrote:
>
> Hi Everybody,
>
> What is the difference between creating a rule and a trigger?
>
http://www.postgresql.org/docs/current/static/rules-triggers.html
--
Milen A. Radev
---(end of broadcast)---
TIP 3: Have
Hello,
I'm testing my PITR recovery procedures and something doesn't look
right.
The following is from the logs upon starting postgres with
recovery.conf file in place
2007-03-23 05:56:00 MDTLOG: database system was interrupted at
2007-03-18 05:09:15 MDT
@ 2007-03-23 05:56:00 MDTLOG: st
Ayuda por favor
Cuando ejecuto este comando me sale una doble tupla del usuario
postgres, esto me error cuando ejecuto el comando
Pg_dump para realizar el respectivo backup..
radar=# select * from pg_user;
usename | usesysid | usecreatedb | usesuper | usecatupd | passwd |
valuntil | useconf
Ayuda por favor
Cuando ejecuto este comando me sale una doble tupla del usuario
postgres, esto me error cuando ejecuto el comando Pg_dump para realizar
el respectivo backup..
radar=# select * from pg_user;
usename | usesysid | usecreatedb | usesuper | usecatupd | passwd |
valuntil | useconfig
On Fri, Mar 23, 2007 at 06:01:17PM -0400, Tom Lane wrote:
> Ray Stell <[EMAIL PROTECTED]> writes:
> > I was hoping to not have to support client certs. I want
> > encryption and to verify the server, but no to verify the client.
> > Does this work and I've got the config wrong?
>
> Maybe I misund
14 matches
Mail list logo
