Hi,
Bit of background:
PGPOOL (V8 with PG 803) talking
to 2 x Red Hat ES4, HP DL 380s with 2Gb RAM and twin CPUs running PG 807
Last night PGPOOL alerted our
OOH on call guy saying that it could communicate with the second DB server
In the PG log file the
errors were:
20
Need Help. Need to upgrade our postgres 7.4 database to 8.1 in order to
upgrade our Lyris Listmanager from 8.1 to 9. I am running into
problems. I get invalid UTF-8 byte sequences. We are running Linux
RedHat AS3. The database dump is 4.5 Gig. I tried the command iconv -c
-f UTF-8 -t UTF-8 -
I had the same problem last week. iconv cleaned up my dump file, but
removed characters I actually wanted (degree & micro symbols). I tried
changing the encoding to Latin1 in my pg_dumpall file. This did seem to
help some, though there was still a problem with some of the characters.
I fina
I'm seeing a background writer process in an 8.0.8 installation that uses 1.6
GB of main memory, and ps shows that it has used an unreasonable amount of
CPU time so far. It seems that the machine was under heavy load just before
I got to it; maybe that is cause? Has anyone seen this sort of me
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I'm seeing a background writer process in an 8.0.8 installation that uses 1.6
> GB of main memory, and ps shows that it has used an unreasonable amount of
> CPU time so far. It seems that the machine was under heavy load just before
> I got to it; m
"Nigel Bishop" <[EMAIL PROTECTED]> writes:
> In the PG log file the errors were:
> 2006-08-03 21:49:18 BST FATAL: invalid frontend message type 50
> 2006-08-03 21:49:18 BST LOG: unexpected EOF on client connection
> 2006-08-03 21:49:18 BST LOG: unexpected EOF on client connection
These look to
I don't have root access here at work, and I wanted to run a jabber
server to communicate with other folks here.
I choose PostgreSQL as db backend.
It is already installed, but it's not starting on boot. I don't have
the password for the postgres user, so I'm running the postmaster
daemon as my o
Am Freitag, 4. August 2006 17:00 schrieb Tom Lane:
> Are you sure it's bloat, and not just a reflection of the fact that it's
> touched every page of the shared buffers over its lifespan?
That seems to be the explanation.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Am Freitag, 4. August 2006 17:57 schrieb Rodolfo Borges:
> $psql -U jabberd2 jabberd2
> psql: FATAL: IDENT authentication failed for user "jabberd2"
You need to read up on configuring the client authentication. If you don't
have root access, ident is probably not a good choice. In particular .
I am trying to
restore a database from a pg_dump.
I have a problematic
issue in that a few rows have a problem with UTF-8 encoding.
All of these rows
are in a specific table.
Is there something I
can run against the table which will validate the rows which have the bad data
and delete the r
I modified one of the .CONF files located in the Postgresql\Data Folder. I
just changed the amout of shared_Buffer from 1000 to 100 and Max_Connections
from 100 to 2.
But after that the PGSQL service stopped working. It stopped listening to
the local host. I have installed PostgreSQL on my deskto
On 8/4/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Am Freitag, 4. August 2006 17:57 schrieb Rodolfo Borges:
> $psql -U jabberd2 jabberd2
> psql: FATAL: IDENT authentication failed for user "jabberd2"
You need to read up on configuring the client authentication. If you don't
have root acces
Am Freitag, 4. August 2006 19.06 schrieb Benjamin Krajmalnik:
> I am trying to restore a database from a pg_dump.
> I have a problematic issue in that a few rows have a problem with UTF-8
> encoding.
> All of these rows are in a specific table.
> Is there something I can run against the table which
The problem is that I do not which rows have the problem.
Out of a few thousand rows, there are only about 15 rows with the
problem.
I was wondering if there is some validation which I can run as a script
against the table so it wil delete it.
How much faster is the copy method as opposed to the i
Hello,
If I want data to come out from my DB which is UTF8 into LATIN1 or
SQL_ASCII. How do I do it. How do I handle the "ô" characters. WIll it come
out the same as in the DB?
Thanks
Abu
---(end of broadcast)---
TIP 2: Don't 'kill -9' the p
Benjamin Krajmalnik wrote:
The problem is that I do not which rows have the problem.
Out of a few thousand rows, there are only about 15 rows with the
problem.
I was wondering if there is some validation which I can run as a script
against the table so it wil delete it.
How much faster is the co
I installed postgresql on my account, and now it works ok.
Thanks again.
On 8/4/06, Rodolfo Borges <[EMAIL PROTECTED]> wrote:
On 8/4/06, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Am Freitag, 4. August 2006 17:57 schrieb Rodolfo Borges:
> > $psql -U jabberd2 jabberd2
> > psql: FATAL: IDENT a
You can set the client encoding to latin1 to make the database convert the
strings for you. Read also chapter 20.2. Character Set Support of the server
documentation about the different options for setting the client encoding.
By the way SQL_ASCII is not a clientencoding in that sens but the lack
18 matches
Mail list logo
