The PostgreSQL developers team lives here. Discussion of current development issues, problems and bugs, and proposed new features. If your question cannot be answered by people in the other lists, and it is likely that only a developer will know the answer, you may re-post your question in this list. You must try elsewhere first!
| Thread | Author | Time |
|---|---|---|
| Re: plpgsql FOR loop doesn't guard against strange step values | Tom Lane | 00:04 |
| Re: plpgsql FOR loop doesn't guard against strange step values | Andrew Dunstan | 00:15 |
| Re: has anyone looked at burstsort ? | Martijn van Oosterhout | 01:15 |
| Warning for exceeding max locks? | Joshua D. Drake | 01:19 |
| Re: Warning for exceeding max locks? | Tom Lane | 02:23 |
| pg_dump ignore tablespaces | Gavin M. Roy | 02:30 |
| Re: pg_dump ignore tablespaces | Tom Lane | 02:56 |
| Re: plpgsql and qualified variable names | Pavel Stehule | 04:53 |
| Re: plpgsql and qualified variable names | Pavel Stehule | 05:00 |
| Re: Warning for exceeding max locks? | Joshua D. Drake | 14:54 |
| Re: compiler warnings on the buildfarm | Stefan Kaltenbrunner | 18:00 |
| Re: plpgsql and qualified variable names | Simon Riggs | 22:16 |
| Re: compiler warnings on the buildfarm | Tom Lane | 22:26 |
| Re: compiler warnings on the buildfarm | Gregory Stark | 22:44 |
| pgsql: Silence Solaris compiler warnings, per buildfarm. | Tom Lane | 22:49 |