| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dawid Kuroczko <qnex42(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Delay INSERT |
| Date: | 2005-03-23 17:33:00 |
| Message-ID: | 8115.1111599180@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-php |
Dawid Kuroczko <qnex42(at)gmail(dot)com> writes:
> PostgreSQL doesn't have such issues with blocking, so only difference
> between INSERT and INSERT DELAYED from PostgreSQL's standpoint
> would be waiting and not for the result...
With the right client-side code you can transmit multiple queries before
receiving the result from the first one. I don't think libpq in its
current incarnation really supports this, but in principle it's doable.
The interesting questions have to do with error handling: if the
"delayed" insert fails, what happens and what is the impact on
subsequent queries? I have no idea how MySQL defines that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-23 17:51:39 | Re: multi line text data/query ?bug? |
| Previous Message | Tom Lane | 2005-03-23 17:28:22 | Re: backend process |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dawid Kuroczko | 2005-03-25 16:29:09 | Re: Delay INSERT |
| Previous Message | Greg Stark | 2005-03-23 17:02:35 | Re: Delay INSERT |