meets - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread
2024-12-30 09:22:11 | BUG #18757: string_agg function(text, text) design issue (PG Bug reporting form)
meet expectations. Could you optimize `string_agg` or suggest an alternative function to handle such
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (5)
2024-12-25 08:32:08 | Re: Re: BUG #18750: Inappropriate update when it is blocked in RC (yrshen@stu.xidian.edu.cn)
meets the WHERE clause, so no update /* tx2 */ update t set id=999 where id = 2; /* tx2 */ UPDATE
Mailing lists >> pgsql-bugs >> Thread
2024-12-06 23:14:37 | Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows (Tom Lane)
meet the expectation that that directory is for functions that replace missing system-library functionality
Mailing lists >> pgsql-bugs >> Thread
2024-11-28 19:45:06 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now (Tom Lane)
meets our expectations (and then truncate it correctly, too). Probably ... that's been the recommendation
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (3)
2024-09-25 18:10:44 | Re: BUG #18632: Whether you need to consider modifying the array's handling of delimiters (曾满)
meeting people’s expectations is not a > bug. The system is behaving as documented
Mailing lists >> pgsql-bugs >> Thread
2024-08-02 12:04:24 | Re: BUG #18564: Incorrect sorting with using NULLS LAST (NULLS FIRST) (Daniel Verite)
meets the OP's expectations: Best regards, -- Daniel Vérité https://postgresql.verite.pro/ Twitter: @DanielVerite
Mailing lists >> pgsql-bugs >> Thread
2024-06-28 17:24:32 | BUG #18526: 'UPDATE' inconsistency using index scan with 'NOT EXIST' after upgrading to PostgreSQL 16 (PG Bug reporting form)
meet the criteria should be updated regardless of using index scan or seq scan. Actual
Mailing lists >> pgsql-bugs >> Thread
2024-04-27 14:37:56 | Re: BUG #17257: (auto)vacuum hangs within lazy_scan_prune() (Melanie Plageman)
meeting the other criteria for opportunistic freezing, we may decide not to freeze any tuples
Mailing lists >> pgsql-bugs >> Thread
2024-03-21 23:20:11 | Re: Regression tests fail with musl libc because libpq.so can't be loaded (Thomas Munro)
meeting musl halfway: clobber argv, but only clobber environ for the libcs known to tolerate
Mailing lists >> pgsql-bugs >> Thread
2024-02-21 20:34:48 | Re: BUG #18356: Casting values from jsonb_each_text does not respect WHERE filter with (Tom Lane)
meet that condition. But without a self-contained example it's hard to be entirely
Mailing lists >> pgsql-bugs >> Thread
2024-02-17 15:12:15 | Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL); (Francisco Olarte)
meeting one month and one week from now", but it bites you sometimes, like when
Mailing lists >> pgsql-bugs >> Thread
2024-01-27 17:32:08 | Re: BUG #18310: Some SQL commands fail to process duplicate objects with error: tuple already (Yongtao Huang)
meet these errors when I git apply your patch, so I do some tiny formate
Mailing lists >> pgsql-bugs >> Thread
2024-01-22 08:04:01 | MarkBufferDirty Assert held LW_EXCLUSIVE lock fail when ginFinishSplit (起个啥名好呢)
meet the requirements of ginFinishSplit. If a crash occurs when an internal page is split
Mailing lists >> pgsql-bugs >> Thread
2024-01-22 07:59:20 | MarkBufferDirty Assert held LW_EXCLUSIVE lock fail when ginFinishSplit (feichanghong)
meet the requirements of ginFinishSplit. If a crash occurs when an internal page is split
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2023-12-31 11:32:10 | Segmentation fault caused by Postgrest - reateplan.c:6178 - prepare_sort_from_pathkeys (Michael B. Williams)
Meeting With Me