Hi,
I am interested in how to speed up storage. About 1000
or more inserts may need to be performed at a time ,
and before each insert I need to look up its key from
the reference table. So each insert is actually a
query followed by an insert.
The tables concerned are :
CREATE TABLE referencet
the
attributes (only) is a result of a select from another
table. I would be interested in knowing if there is a
way to do that.
> Have you EXPLAINed the SELECT query to see if index
> scans are being used
> where possible?
Yes, the index scans are being used
> -Mitch
>
> - Orig
Hi,
Does anyone know how postgres/ postmaster handles the
situation where the physical hard disk space is full ?
Does it crash / corrupt the database, or does it
cleanly exit with appopriate message so that relevant
tables can be pruned (by the user) to free up disk
space and get it working again
lains that it can't extend the
> table and bails out of
> the transaction. I just wish it didn't happen so
> often...
>
> Mike Diehl,
> Network Monitoring Tool Devl.
> 284-3137
> [EMAIL PROTECTED]
>
>
> > -Original Message-
> > From
Hi,
I was comparing speed of inserts in C vs JDBC and
found that as the table size increases the speed
differential decreases till there is no difference (no
problem). However inserts kept getting slower and
slower as the table size increased and the performance
became quite poor. Here is the dat
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Rini Dutta <[EMAIL PROTECTED]> writes:
> > Here is the performance statistics on the same
> table.
> > Note the fall in performance as the test proceeds.
>
> Try 7.1. I think you are running into the
> lots-of-pe
--- Tom Lane <[EMAIL PROTECTED]> wrote:
> Rini Dutta <[EMAIL PROTECTED]> writes:
> > Here is the performance statistics on the same
> table.
> > Note the fall in performance as the test proceeds.
>
> Try 7.1. I think you are running into the
> lots-of-pe
