atform of choice for heavy data manipulation (I/O).
--
Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/
PGP signature
On Sun, Nov 05, 2000 at 10:41:12PM -0800, Michael Miyabara-McCaskey wrote:
> Out of curiosity, if I were using something else besides "psql" would this
> have still been a problem?
Yes. The library interface in libpq will pull the entire record set
into memory unless you use cu
ecessary.
To answer the second, if you do a plain "SELECT *", it will buffer the
entire response set into RAM before printing anything out. If you have
more than a trivial number of records to fetch from the database (and
5.5GB is certainly more than trivial), use a cursor and only
u're adding or removing files
synchronously.
--
Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/
PGP signature
On Fri, Sep 22, 2000 at 12:03:13PM -0400, Tom Lane wrote:
> Bruce Guenter <[EMAIL PROTECTED]> writes:
> > I've been thinking that one way to emulate replication would be to run a
> > pgsql "shim" that would redirect queries to two back-ends
> > simult
milar situation, where I want to set up two live
redundant sites, where nightly updates aren't an option.
--
Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/
PGP signature
from 'wfoo');
ltrim
---
foo
(1 row)
I ended up writing a function to do it, and for the data sets I'm
dealing with, it's fast enough:
CREATE FUNCTION strip_www (text ) RETURNS text AS
'BEGIN
IF position(''www.'' IN $1) = 1 THEN
RETURN substri
ecent ones linked to from the Slashdot discussion, which only compare
PostgreSQL and MySQL.
Thank you.
--
Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/
PGP signature
me by doing:
create unique index foo_pkey on foo*(id);
but it caused a syntax error. Creating a unique index on just foo
allows duplicates between the two tables.
--
Bruce Guenter, QCC Communications Corp. EMail: [EMAIL PROTECTED]
Phone: (306)249-0220 WWW: http
