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: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation) | Robert Haas | 00:01 |
| Re: Command Triggers, patch v11 | Thom Brown | 00:08 |
| Re: Command Triggers, patch v11 | Robert Haas | 00:12 |
| Re: Command Triggers, patch v11 | [email protected] | 00:39 |
| Re: Command Triggers, patch v11 | Thom Brown | 00:56 |
| Re: review: CHECK FUNCTION statement | Alvaro Herrera | 01:24 |
| Re: review: CHECK FUNCTION statement | Pavel Stehule | 05:25 |
| Re: review: CHECK FUNCTION statement | Pavel Stehule | 05:45 |
| Re: review: CHECK FUNCTION statement | Alvaro Herrera | 06:01 |
| Re: review: CHECK FUNCTION statement | Pavel Stehule | 06:03 |
| Re: RFC: Making TRUNCATE more "MVCC-safe" 📎 | Simon Riggs | 12:53 |
| Re: COPY with hints, rebirth | Simon Riggs | 13:14 |
| Re: review: CHECK FUNCTION statement | Petr Jelínek | 13:26 |
| Re: Command Triggers, patch v11 | Dimitri Fontaine | 13:45 |
| Re: Command Triggers, patch v11 | Thom Brown | 14:03 |