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
Hi,
say I have three tables a,b,c with lots of columns (say 10 for each
table). Using psql command line, why does
SELECT a.*,b.*,c.* FROM a,b,c
takes much more longer (in my specifc case 3 times) than only
selecting one column like
SELECT a.oid, b.oid, c.oid FROM a,b,c.
This is on 7.0. Can
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 run
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.*,
Hi,
can Postgres store binary data in TEXT fields? Or is there a solution
except large objects?
Dirk
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.
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]
Hi,
I don't know if this fits into the current thread but I have also a
problem with backends growing up to 100MB and more. This is on 6.5:
CREATE TABLE docobj (
envelopeOID NOT NULL,
docspec OID,
docindexINTEGER,
attrid INTEGER,
