Re: [ADMIN] Large database help

On Mon, Apr 23, 2001 at 08:15:05PM -0400, [EMAIL PROTECTED] wrote: Then, please correct me if I'm wrong: I should be able to test your hypothesis by creating a small DB (of say 2MB) and setting up at least a dozen backends to tag it. If I get the same symptoms w/ respect to disk

[ADMIN] error compiling 7.1 on Solaris 8 x86 (long)

When i try to compile postgresql on solaris 8/ x86 i get following: make -C tcop all make[3]: Entering directory `/export/home/soft/source/postgresql/7.1/postgresql-7.1/src/backend/tcop' gcc -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../src/includ e -c -o dest.o dest.c gcc

[ADMIN] Re: Large database help

and dropped into a single table, which will become ~20GB. Analysis happens on a Windows client (over a network) that queries the data in chunks across parallel connections. I'm running the DB on a dual gig p3 w/ 512 memory under Redhat 6 (.0 I think). A single index exists that gives the best

[ADMIN] 7.1 performance

Hi there, i just upgraded my database system from 7.0.3 to 7.1 ... i did a dumpall and psql -f dump.sql to the new db. the data is in place correctly and its running fine. but as soon as i put the connections back on to the db the load raised to 6. prior to the upgrade the system load was an 0.3

[ADMIN] Restoring a pg_dump fails with

Hello! By upgrading von PostgreSQL 6.5.3 to 7.1.0 I restored a dump file by psql dbname dbname.dump After some time I get the following message: ERROR: copy: line 1638280, Memory exhausted in AllocSetAlloc(56) PQendcopy: resetting connection The total number of lines is about 10 Millions!

Re: [ADMIN] Users logged !

Luis Sousa writes: Is it possible to see what users are logged into the database using version 7.1 ?? The ps command gives you an idea. You can also look into the logs to see who connected when. Neither of these is ideal, admittedly. -- Peter Eisentraut [EMAIL PROTECTED]

Re: [ADMIN] 7.1 performance

Thomas Heller [EMAIL PROTECTED] writes: is this normal for 7.1 to need so much more hardware? No... i use the same settings for sort_mem, buffers, etc. just no fsync. I thought 7.1 wouldn't need that anymore. Does the behavior change if you turn off fsync again?

[ADMIN] Re: error compiling 7.1 on Solaris 8 x86 (long)

Andrzej Kwiatkowski [EMAIL PROTECTED] wrote: When i try to compile postgresql on solaris 8/ x86 i get following: [lots of warnings and some errors on math.h related stuff like 'ceil', 'floor', 'fabs', 'HUGE_VAL'] It looks like gcc is finding a broken math.h include file - check if you have

Re: [ADMIN] Restoring a pg_dump fails with

On Thu, Apr 26, 2001 at 05:35:02PM +0200, Reiner Dassing wrote: By upgrading von PostgreSQL 6.5.3 to 7.1.0 I restored a dump file by psql dbname dbname.dump After some time I get the following message: ERROR: copy: line 1638280, Memory exhausted in AllocSetAlloc(56) PQendcopy: resetting

[ADMIN] logs

my options in pg_options are: verbose=2 query hostlookup showportnumber syslog=2 what is the line I have to write in the /etc/syslog.conf in order to see events of databases ? __ Voila vous propose une boite aux lettres gratuite sur Voila

[ADMIN] Can't start Pgsql 7.1 on FreeBSD 4.2

Postmaster spits out this : IpcMemoryCreate: shmget(key=5432001, size=1236992, 03600) failed: Cannot allocate memory When I try to start it. I compiled and installed from the ports collection. I compiled these into my kernel : options SYSVSHM #SYSV-style shared

Re: [ADMIN] random rows

thanks. Jie LIANG St. Bernard Software 10350 Science Center Drive Suite 100, San Diego, CA 92121 Office:(858)320-4873 [EMAIL PROTECTED] www.stbernard.com www.ipinc.com On Thu, 26 Apr 2001, Ing. Roberto Andrade Fonseca wrote: On Thu, 26 Apr 2001, Jie Liang wrote: How I can return

[ADMIN] Re: random rows

On Thu, 26 Apr 2001, Jie Liang wrote: I've donne something like: prereg_iw=# select random(), nombre from asistente order by 1 limit 10; random|nombre --+--- 0.000214523170243261 | ALFONSO 0.000478655100091666 | OSCAR

[ADMIN] Performance with Large Volumes of Data

Hi, I am non a real sysadmin or dba, but got stuck doing it and am trying to learn via a fairly difficult problem that my group must deal with: a LARGE volume of data. I have been working from scratch on this for about 3 weeks and have runs lots of tests. I am running postgres7.1 on a

Re: [ADMIN] Can't start Pgsql 7.1 on FreeBSD 4.2

Kurt Seel [EMAIL PROTECTED] writes: Postmaster spits out this : IpcMemoryCreate: shmget(key=5432001, size=1236992, 03600) failed: Cannot allocate memory If you try, say, -N 8 -B 16 does it start? I'm betting 1236992 bytes is larger than your kernel's limit on shared memory segment size.

[ADMIN] Re: [SQL] select ... for update in plpgsql

'select ... for update' needs to be inside a transaction. plpgsql cannot start or end transactions. 'begin' and 'end' are not transaction statements. (read the docs). -Cedar On Fri, 20 Apr 2001, Jie Liang wrote: Hi, I have a question about 'select ... for update'; according to the

[ADMIN] Users logged !

Is it possible to see what users are logged into the database using version 7.1 ?? Luis Sousa ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

[ADMIN] Sort in PostgreSQL

Hello, I am with a problem in the SAGU (http://sagu.codigoaberto.org.br), more specifically in the Postgres (we use version 6.5.3) with the sort of names. It separates capital and lowcase letters and letters with and without accents. After one he searches, we find that we

Re: [ADMIN] error compiling 7.1 on Solaris 8 x86 (long)

Andrzej Kwiatkowski [EMAIL PROTECTED] writes: When i try to compile postgresql on solaris 8/ x86 i get following: gcc -Wall -Wmissing-prototypes -Wmissing-declarations -I../../../../src/inc lude -c -o float.o float.c float.c: In function `CheckFloat4Val': float.c:149: warning: type