throw date - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread
2024-10-03 19:24:18 | BUG #18645: Change between 16 and 17 when attaching partitions and the root tbl has (PG Bug reporting form)
date_time timestamp with time zone NOT NULL DEFAULT CURRENT_TIMESTAMP, message_id bigint NOT NULL GENERATED ALWAYS AS IDENTITY ( INCREMENT 1 START 1 MINVALUE 1 MAXVALUE 9223372036854775807 CACHE 1 ) ) PARTITION BY LIST (device
Mailing lists >> pgsql-bugs >> Thread
2024-08-01 01:37:45 | Re: Inconsistency of timezones in postgresql (Chris BSomething)
date in the future, even though the field is populated with a default clause of "current_timestamp". select now() at time zone UTC returns the correct thing. Is it wrong to assign current_timestamp
Mailing lists >> pgsql-bugs >> Thread
2024-07-20 16:26:29 | Re: BUG #18546: Attempt to insert default into a non-updatable column of a view (Tom Lane)
dating AFAICS to Dean's cab5dc5da) already point out that rewriteTargetListIU can add targetlist items, but we missed the fact that it can delete them too. So it seems like what we need
Mailing lists >> pgsql-bugs >> Thread
2024-07-01 15:08:29 | BUG #18527: Imported data using a csv file and made a latest entry into same (PG Bug reporting form)
date.strftime('%d%m%Y')}{str(int(lastRow[15:18]) + 1).zfill(3)}" return ProjectCode The difference in ordering of entries between importing data from csv and manually creating a new entry into the table
Mailing lists >> pgsql-bugs >> Thread
2024-06-12 23:24:46 | Re: BUG #18497: Heap-use-after-free in plpgsql (Tom Lane)
throw an error, + * in which case the expr is left marked "not simple", which is fine.) + */ + oldcontext = MemoryContextSwitchTo(get_eval_mcontext(estate)); + cplan = SPI_plan_get_cached_plan(expr->plan); + MemoryContextSwitchTo(oldcontext); + + /* Can't fail
Mailing lists >> pgsql-bugs >> Thread
2023-11-24 18:01:02 | Re: BUG #18214: poly_contain (@>) hangs forever for input data with zeros and infinities (Tom Lane)
Date: Sat Nov 21 16:46:43 2020 -0500 Fix FPeq() and friends to get the right answers for infinities. I'm inclined to think that poly_contain_poly, or more specifically lseg_inside_poly
Mailing lists >> pgsql-bugs >> Thread
2023-03-17 02:34:53 | Re:Re: BUG #17845: insert into on conflict bug . (德哥)
Throwing an error here is obviously not logically correct.
在 2023-03-16 22:28:27，"jian he"
Mailing lists >> pgsql-bugs >> Thread
2023-02-15 05:06:12 | Re: BUG #17791: Assert on procarray.c (Andres Freund)
Date: 2020-02-24 17:28:33 -0500 Account explicitly for long-lived FDs that are allocated outside fd.c. But I can't yet explain precisely why that causes the assertion failures. A vague guess
Mailing lists >> pgsql-bugs >> Thread
2022-05-03 22:35:11 | Re: Types pollution with iso-8859-1 oids and server-side parameters binding (Daniele Varrazzo)
date type is chosen arbitrarily, possibly depending on the way the parsed query is traversed building the plan? Looking at the above variation of the problem, maybe the right thing to do would
Mailing lists >> pgsql-bugs >> Thread
2021-05-19 05:04:07 | Re:Fwd: BUG #17017: Two versions of the same row of records are returned in (李可强)
Date: 2021年5月19日周三 00:18
Subject: Re: BUG #17017: Two versions of the same row of records are returned in one query
To:
Mailing lists >> pgsql-bugs >> Thread
2020-10-06 23:45:51 | BUG #16658: HSTORE typecast exception is XX000 - inconsistent with the other cast exceptions (22xxx) (PG Bug reporting form)
DATE, 'abc'::INTEGER, '123'::TIMESTAMPTZ. HSTORE type casting seems to be breaking out from the pack throwing
Mailing lists >> pgsql-bugs >> Thread
2020-10-04 16:18:43 | BUG #16653: Regression in CTE evaluation (PG Bug reporting form)
throwing an error in version 13. CREATE TABLE test AS SELECT now() AS tstmp, 'value' AS val; WITH exp_days AS ( SELECT ''::TEXT AS days WHERE '' ~ E'^[-]?\\d+$' ) SELECT test.* FROM test CROSS JOIN
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2020-09-29 21:36:02 | ERROR: insufficient columns in the PRIMARY KEY constraint definition (Nagaraj Raj)
throwing below error: ERROR: insufficient columns in the PRIMARY KEY constraint definitionDETAIL: PRIMARY KEY constraint on table "l_billing_account_p" lacks column "load_dttm" which is part of the partition key.SQL state: 0A000
Mailing lists >> pgsql-bugs >> Thread
2020-05-28 00:21:26 | Re: Explicit deterministic COLLATE fails with pattern matching operations on column with non-deterministic collation (Tom Lane)
throws an error. The idea that using the "wrong" collation might actually cause an error was not factored into this design, obviously. I'm not sure offhand what to do about
Mailing lists >> pgsql-bugs >> Thread
2020-01-17 14:59:42 | Re: BUG #16216: the result of to_date function with negative year number not same (Tom Lane)
throw an error for zero or negative year field. OTOH, the point of to_date