unsubscribe
Regards,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ivo Rossacher
Sent: Wednesday, March 22, 2006 3:08 AM
To: pgsql-admin@postgresql.org
Cc: Ben K.
Subject: Re: [ADMIN] encoding question
Am Dienstag, 21. März 2006 21.14 schrieb Ben K.:
unsubscribe
Regards,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ben K.
Sent: Tuesday, March 21, 2006 10:09 PM
To: Tom Lane
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] encoding question
>> ERROR: invalid UTF-8 byte sequence detected nea
"Sriram Dandapani" <[EMAIL PROTECTED]> writes:
> Why doesn't Postgres use swap in this situation
Perhaps you need to adjust the ulimit settings that the postmaster is
started under.
regards, tom lane
---(end of broadcast)---
Some more interesting information.
The insert statement is issued with a jdbc callback to the postgres
database (because the application requires partial commits...equivalent
of autonomous transactions)
What I noticed was that the writer process when using the jdbc insert
was very active consumin
-Original Message-
From: Sriram Dandapani
Sent: Tuesday, March 21, 2006 4:01 PM
To: 'Tom Lane'
Subject: RE: [ADMIN] out of memory error with large insert
Upon monitoring with top, the insert statement process keeps eating up
memory until there is nothing left on the linux box
Why does
"Sriram Dandapani" <[EMAIL PROTECTED]> writes:
> On a large transaction involving an insert of 8 million rows, after a
> while Postgres complains of an out of memory error.
If there are foreign-key checks involved, try dropping those constraints
and re-creating them afterwards. Probably faster th
Hi
On a large transaction involving an insert of 8 million
rows, after a while Postgres complains of an out of memory error.
Failed on request of size 32
I get no other message.
Shmmax is set to 1 Gb
Shared_buffers set to 5
Max memory on box is 4Gb..Postgres is the
Am Dienstag, 21. März 2006 21.14 schrieb Ben K.:
> I just wanted to add that when I created the same database with -E
> SQL_ASCII on my linux box, the dump was loaded fine. I created another
> database without -E and observed the same invalid encoding problem.
This is not really surprising since S
I just wanted to add that when I created the same database with -E
SQL_ASCII on my linux box, the dump was loaded fine. I created another
database without -E and observed the same invalid encoding problem.
On the face value this seems to solve the problem at least superficially.
I'd like to
it was a hasty post. Sorry
On 3/22/06, Marc G. Fournier <[EMAIL PROTECTED]> wrote:
>
> Vote for what? There isn't a single PostgreSQL product in there ... and
> I'm not voting for phpMyAdmin or Firebird :(
>
>
> On Wed, 22 Mar 2006, Vishal Kashyap wrote:
>
> > http://www.wilsonresearch.com/2006/
Vote for what? There isn't a single PostgreSQL product in there ... and
I'm not voting for phpMyAdmin or Firebird :(
On Wed, 22 Mar 2006, Vishal Kashyap wrote:
http://www.wilsonresearch.com/2006/ostgawards06/ostgawards2.php
--
With Best Regards,
Vishal Kashyap.
http://www.vishal.net.in
-
http://www.wilsonresearch.com/2006/ostgawards06/ostgawards2.php
--
With Best Regards,
Vishal Kashyap.
http://www.vishal.net.in
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On Thu, Mar 16, 2006 at 08:34:19PM +0100, Matze wrote:
> Hallo There,
>
> I've got a Problem with PostgreSQL. I installed the Windows Binary of
> Postgre 8.1 (postgresql-8.1.msi). During the Installation the Installer
> popped up several messages that some Propertys of the Server or the Tables
> c
On Thu, Mar 16, 2006 at 05:17:47PM +0100, ute wrote:
> Typical situation is, that ended sql commands not ends postmaster
> processes. For example when I run vacuum full analyze some database, sql
> command ends, but process not! Then I can see this:
>
> 62123 ?? D 0:22,24 postmaster: post
On Mon, Mar 20, 2006 at 10:03:28AM -0800, Dianne Yumul wrote:
> On Mar 18, 2006, at 6:15 PM, Bruce Momjian wrote:
>
> >Luis P. Mendes wrote:
> >>When I connect to a database via psql and do a select * from table; I
> >>get the first page of results, considering \pset pager is on.
> >>
> >>In Debia
ERROR: invalid UTF-8 byte sequence detected near byte 0x85
Looks to me like it might have been meant as LATIN1 or one of
the other single-byte ASCII-extension encodings.
Thanks. Indeed it has non-ascii and wouldn't be covered by SQL_ASCII, I
see now.
I never suspected there'd be non-ascii i
Thanks John and Ivo for help.
It turned out that I had to manually SET CLIENT_ENCODING TO 'LATIN1' before
processing the dump (which didn't have this specified). This fixed the problem.
I thought a DB set to UNICODE char encoding (server_encoding) would process the
Extended ASCII characters, bu
17 matches
Mail list logo