I wrote:
> We could perhaps do better by doing the initial addition of the
> interval and seeing if that produces a value greater than, less
> than, or equal to the start timestamp. But I'm afraid that
> doesn't move the goalposts very far, because as this example
> shows, we might get different r
Jakob Teuber writes:
> I noticed, that the following query will send Postgres into an infinite
> loop:
> (a) select generate_series(timestamp '2025-01-30', timestamp
> '2025-02-01', interval '1 month -29 days');
> One could certainly argue that “go and do an infinite loop” is plainly
> the int
Hi all,
I noticed, that the following query will send Postgres into an infinite
loop:
(a) select generate_series(timestamp '2025-01-30', timestamp
'2025-02-01', interval '1 month -29 days');
Adding one month to 2023-01-30 will result in 2023-02-28 due to February
having no 31st day, and t
On Mon, 2025-03-03 at 07:14 +0330, me nefcanto wrote:
> The point is, that there is already an `on_error ignore` clause there. This
> means that
> somewhere there is a try/catch per row. If I'm wrong, please let me know.
The crucial point that Tom referred to is the "per row". What is a row?
Im
