pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
to do's?
2+ messages / 2 participants
[nested] [flat]

* to do's?
@ 1999-09-14 21:53 Clayton Cottingham <drfrog@smartt.com>
  1999-09-15 13:53 ` Re: [SQL] to do's? Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 2+ messages in thread

From: Clayton Cottingham @ 1999-09-14 21:53 UTC (permalink / raw)
  To: pgsql-sql


hi i was wondering if multi threading will be enabled soon?

also
a prob im having which might be query related but a todo as well
is that i have a 1.3 mil row db
when i try to select all i get memory out type errors, either system wide or
droping the backend

even when i go over 1/4 of the size this happens, can there be some sort of
improvements in the memory handling here too?

or is this an sql technique i dont realize?

basically im selecting rows from the 1.3 mil table and inserting certain
columns into another after some processing

im basically using
select field1,field2 ,field3 from table

and the preprocess and
insert into othertable values field1 ,filed2 ,field3

even if i reduce the select statement to half the size of the first table it
still cans out

any help appreciatted
!







^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: [SQL] to do's?
  1999-09-14 21:53 to do's? Clayton Cottingham <drfrog@smartt.com>
@ 1999-09-15 13:53 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 1999-09-15 13:53 UTC (permalink / raw)
  To: Clayton Cottingham <drfrog@smartt.com>; +Cc: pgsql-sql

Clayton Cottingham <drfrog@smartt.com> writes:
> hi i was wondering if multi threading will be enabled soon?

Huh?  We already have multiple backends, what advantage would
there be to using threads?

> is that i have a 1.3 mil row db when i try to select all i get memory
> out type errors, either system wide or droping the backend

The problem is probably at the application end --- libpq is built on
the model that it can collect the entire query result in memory and
then give the application random access to that array.  So if the
query result won't fit in the space available to the application,
trouble.  I don't see why this would affect anything else in your
system, though, unless the app uses up all available swap space and
holds it for a while before crashing...

What you probably want to do instead of a straight SELECT is use
DECLARE CURSOR and FETCH to retrieve the table a few dozen/hundred
rows at a time.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~1999-09-15 13:53 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-09-14 21:53 to do's? Clayton Cottingham <drfrog@smartt.com>
1999-09-15 13:53 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox