| From: | "Nicolas Bazin" <nbazin(at)ingenico(dot)com(dot)au> |
|---|---|
| To: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | timeout implementation issues |
| Date: | 2002-04-24 00:04:06 |
| Message-ID: | 002101c1eb23$8d3db9e0$660d090a@software.ingenico.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I also want to implement the same feature but for ecpg. On INFORMIX there is the following syntax to control timeouts:
SET LOCK MODE TO [WAIT [seconds] | NO WAIT]
There is 2 possibilities:
- either the pre-processor implements execution of the statement with the asynchronous functions. Then I have 2 issues, the polling delay will slow down the transaction performance, and I don't have a way to implement the NO WAIT for I would have to know if the statement is being processed right away or is waiting for another transaction to complete.
- the backend implements this syntax and returns an error code for timeout.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-04-24 00:24:47 | Re: ?Missing '#define FUNC_MAX_ARGS' in pg_config.h.win32? |
| Previous Message | Bruce Momjian | 2002-04-23 23:54:53 | Re: What is wrong with hashed index usage? |