| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Adam Haberlach <adam(at)newsnipple(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Sluggish inserts/updates ? |
| Date: | 2001-02-07 22:27:32 |
| Message-ID: | 3A81CBD4.E444FF8D@tm.ee |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Adam Haberlach wrote:
>
> I've got a system in which a row is being created by one process,
> a notify is sent, and another process finds and then deletes the
> row. This whole interchange seems to be taking about a second, which
> seems oddly slow.
If you do it enough times without vacuum, the table grows quite big,
even
though it may look empty...
> As far as I know, I have the fsync-on-anything
> turned off (*).
>
> I'm mainly wondering if I should index/not index the key of the
> table, and if I should blame the hardware or Postgres?
Index would very likely help. (BTW, the best way to find out is to try
it -
you can always drop it later ;)
> The hard
> drive on the R&D server is pretty slow, although the CPU is pretty
> dang fast. I could also blame the notification system but that
> shouldn't be a problem, right?
How do you read the notify ?
----------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kovacs Zoltan | 2001-02-07 22:46:17 | pg_dump: oldie but goldie |
| Previous Message | Lamar Owen | 2001-02-07 22:27:00 | Re: pg_ctl changes |