On 5 Jun 2010, at 4:44, Wang, Mary Y wrote:
> Hi,
>
> I'm getting this error from postgres " ERROR: character 0x90 of encoding
> "WIN1252" has no equivalent in "UTF8" " and from a dump file when I tried to
> use psql command to restore the dump.
>
> I have SET client_encoding = 'win1252' in
On Thu, Jun 3, 2010 at 2:14 AM, Kevin Grittner
wrote:
> Manohar Bhattarai wrote:
>
> > FATAL: password authentication failed for user "postgres"
>
> > But the password is the same that i use to login postgres user in
> > the terminal.
> > What could be the problem?
>
> When you say "postgres user
"Ken Winter" writes:
> When the run-time parameter transform_null_equals is on, shouldn't two
> variables with NULL values evaluate as equal?
No. That setting does not change the runtime behavior of comparison.
The only thing it does is change the literal syntax "something = NULL"
to "something
Thanks Alban, but I'm still confused.
I just read the PostgreSQL manual, and got the impression that UTF8 would take
care of ALL character sets, so I put SET client_encoding = 'UTF8' in the dump
file, and reload it again, then I got even more errors like:
psql:/tmp/060410finalsr15dump.txt:31430:
Frank van Vugt writes:
> One might consider adding a single line to the end of 9.9 of the docs that
> warns for this behaviour and/or add the specific example?
I put some more explanation and examples into the 9.0 docs:
http://developer.postgresql.org/pgdocs/postgres/functions-datetime.html
I get it. Thanks, Tom.
In case anybody else needs this functionality, let me offer a family of
functions that do comparisons that treat NULL as a real value (rather than
as "unknown"). For example:
CREATE OR REPLACE FUNCTION eqnull(varchar, varchar) RETURNS boolean AS
$BODY$
/*
Return True if b
On 5 Jun 2010, at 16:07, Wang, Mary Y wrote:
> Thanks Alban, but I'm still confused.
> I just read the PostgreSQL manual, and got the impression that UTF8 would
> take care of ALL character sets, so I put SET client_encoding = 'UTF8' in the
> dump file, and reload it again, then I got even more
On Jun 5, 2010, at 9:46 AM, Ken Winter wrote:
> I get it. Thanks, Tom.
>
> In case anybody else needs this functionality, let me offer a family of
> functions that do comparisons that treat NULL as a real value (rather than
> as "unknown"). For example:
You should take a look at "is not disti
On Saturday 05 June 2010 7:07:35 am Wang, Mary Y wrote:
> Thanks Alban, but I'm still confused.
> I just read the PostgreSQL manual, and got the impression that UTF8 would
> take care of ALL character sets, so I put SET client_encoding = 'UTF8' in
> the dump file, and reload it again, then I got ev
Steve ~
Thanks for the great tips. See comments below.
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Steve Atkins
> Sent: Saturday, June 05, 2010 1:04 PM
> To: PostgreSQL pg-general List
> Subject: Re: [GENERAL
2010/6/4 Wang, Mary Y :
> Hi,
>
> I'm getting this error from postgres " ERROR: character 0x90 of encoding
> "WIN1252" has no equivalent in "UTF8" " and from a dump file when I tried to
> use psql command to restore the dump.
>
> I have SET client_encoding = 'win1252' in the dump file.
>
> Any
Mario Ignacio Rodríguez Cortés writes:
> Well, i have a question if you know about this, i have a webserver in a
> server and i have a database server, the question is: where should I
> install the pgbouncer? in webserver, in database server or is the same?
> whats your experience.
I always insta
"Ken Winter" writes:
> In case anybody else needs this functionality, let me offer a family of
> functions that do comparisons that treat NULL as a real value (rather than
> as "unknown"). For example:
Er ... this'd be a lot shorter using IS [NOT] DISTINCT FROM.
regards,
I'm curious if anyone has had any experiences (good and bad) using
Postgres on Dell PowerEdge servers.
My manager and I are looking at replacing a Sun x4540 server with a Dell
server connected to a disk subsystem (or two). We're looking at the
R710 servers connected to an MD1220 I believe (I'
u235sentinel wrote:
I'm curious if anyone has had any experiences (good and bad) using
Postgres on Dell PowerEdge servers.
Poweredge is a brandname that describes every single server Dell has
sold since about 15 years ago, maybe more. I had a Poweredge that was
a dual 600Mhz pentium-III w/
Hi,
I have a doubt about JOINS.
What is the difference between:
1. SELECT b.* from banners b, banners_users bu where b.id = bu.bid and
bu.uid = 5;
2. SELECT b.* from banners b INNER JOIN banners_users bu ON b.id =
bu.bid AND bu.uid = 5;
What is the first type of join called ?
and is it possibl
On Sat, Jun 5, 2010 at 5:27 PM, u235sentinel wrote:
> I'm curious if anyone has had any experiences (good and bad) using Postgres
> on Dell PowerEdge servers.
I've had lots of experience with Dell, most of it poor. Wrong upgrade
CPUs, use of non-buffered memory meaning I can't max out my machine
17 matches
Mail list logo
