[GENERAL] Will there be replication support in 7.1 from erserver.com ?

2000-11-23 Thread Dirk Lutzebaeck


Subject says it all I guess. What is the relationship between 7.1 and
the new features added by www.erserver.com (ie. adding replication
functionality to Postgresql which will be open source)?

Dirk



Re: [GENERAL]COPY still running

2000-01-26 Thread Dirk Lutzebaeck

Arnaud FLORENT writes:
  Hello i start yesterday afternoon a COPY command into a table.
  the file is 15 Mb
  i've set triggers before and after insert on the table
  the before trigger just perform data check.
  the after trigger update a 10 000 rows linked table.
  
  the COPY command runs all the night ad has not yet finished...
  
  what is the problem
  

You probably have indexes defined on this table. You should drop all
the indexes before the copy and create them after the copy if the
number of rows in the copy commands exceeds the number of the current
rows in the table.

I have dropped the indexes while copy'ing which seems to be no
problem. Just create them after the copy is finished. Ymmv...

Dirk





[GENERAL] vacuum analyze: Tuple is too big (corrupts DB?)

1999-12-13 Thread Dirk Lutzebaeck


Hello,

when I vacuum analyze my db (6.5.3 on Linux) I cannot access
some data afterwards because the vacuum terminates with

ERROR:  Tuple is too big: size 8596

I did pg_dump -o and read in back again, still the same error. 

Eg. accessing data after vacuum results in

SELECT envpart_map.*,
   envpart_map.oid AS recioid,
   member.*,
   member.oid AS memoid
   WHERE envpart_map.member=member.oid
   AND envpart_map.role  0
   AND envpart_map.envelope IN (1072343,1073358,1074472,1073722,14235
82)': pqReadData() -- backend closed the channel unexpectedly.


Where can I get on from here?

Dirk





Re: [GENERAL] pgaccess removed from 6.5.2?

1999-09-22 Thread Dirk Lutzebaeck

Palle Girgensohn writes:
  Bruce Momjian wrote:
   
The release notes talk about pgaccess beeing updated, but it is removed
from the tarball? Only docs and demos are left; Makefile and tcl code is
gone. How come?
   
/Palle
   
   Not sure how that happened.  I see it here.

  Well, it's not in the tarball. Here's an ls -l src/bin/pgaccess
  total 7
  drwxr-xr-x   7 girgen  wheel  512 Sep 16 02:22 ./
  drwxr-xr-x  21 girgen  wheel  512 Sep 16 02:22 ../
  drwxr-xr-x   2 girgen  wheel  512 Sep 16 02:22 demo/
  drwxr-xr-x   3 girgen  wheel  512 Sep 16 02:22 doc/
  drwxr-xr-x   2 girgen  wheel  512 Sep 16 02:22 images/
  drwxr-xr-x   4 girgen  wheel  512 Sep 16 02:22 lib/
  drwxr-xr-x   3 girgen  wheel  512 Sep 16 02:22 win32/
  
  In 6.5.1, there was a Makefile and pgaccess.tcl in there, but not
  anymore. The Makefile in src/bin has references to the now non-existing
  Makefile.


Same with me, I used the patch. ls -l src/bin/pgaccess

drwxr-xr-x   2 uucp wheel1024 Jul 20 14:15 CVS/
-rw-r--r--   1 uucp wheel 207 Nov  6  1998 a_right.gif
drwxr-xr-x   2 root root 1024 Sep 22 10:55 demo/
drwxr-xr-x   3 root root 1024 Sep 22 10:55 doc/
drwxr-xr-x   4 root root 1024 Sep 22 10:55 lib/
-rw-r--r--   1 uucp wheel   48128 Dec 12  1998 libpgtcl.dll
-rw-r--r--   1 uucp wheel   78336 Dec 12  1998 libpq.dll

Dirk






[GENERAL] Binary data?

1999-09-22 Thread Dirk Lutzebaeck


Hi,

can Postgres store binary data in TEXT fields? Or is there a solution
except large objects?

Dirk





[GENERAL] backend crashing with INTERSECT / ORDER BY

1999-08-20 Thread Dirk Lutzebaeck


So I tried INTERSECT with ORDER BY and it crashes on 6.5 and 6.5.1:

[csmaster@kamet release0]$ psql cs1
Welcome to the POSTGRESQL interactive sql monitor:
  Please read the file COPYRIGHT for copyright terms of POSTGRESQL
[PostgreSQL 6.5.1 on i686-pc-linux-gnu, compiled by gcc egcs-2.91.66]

   type \? for help on slash commands
   type \q to quit
   type \g or terminate with semicolon to execute query
 You are currently connected to the database: cs1

cs1= SELECT envelope FROM docobj
cs1- WHERE attrid=5
cs1- INTERSECT
cs1- SELECT envelope FROM docobj
cs1- WHERE attrid=6
cs1- ORDER BY attrid DESC
cs1- ;
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
We have lost the connection to the backend, so further processing is impossible.  
Terminating.

Any clues?

Dirk