validly - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread
2025-06-06 08:54:40 | Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without (Michael Paquier)
valid input. - xmlXPathCompiledEval, where valid input is expected. - xmlXPathNewContext, which is incorrect, could fail an allocation
Mailing lists >> pgsql-bugs >> Thread
2025-05-31 21:32:10 | Re: [bug] keyword commit being accepted for column name (David G. Johnston)
valid here, if you double-quote an identifier it never is even possibly considered a keyword
Mailing lists >> pgsql-bugs >> Thread
2025-05-14 06:27:14 | BUG #18926: PostgreSQL 17.5 produces malformed binary COPY output (`GPOCYP` instead of `PGCOPY`) across platform (PG Bug reporting form)
valid binary COPY stream and results in errors like `COPY file signature not recognized`. --- ### Environment
Mailing lists >> pgsql-bugs >> Thread
2025-05-03 19:50:00 | Planner does not use btree index for LIKE 'prefix%' on text column, but does for (Abdullah DURSUN)
valid and ready. - The planner does not use the index for LIKE 'prefix%', but does
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-04-22 23:53:23 | Re: Command order bug in pg_dump (Tom Lane)
valid_at = daterange('2016-02-01', '2016-03- -- should fail: UPDATE temporal_partitioned_rng SET valid
Mailing lists >> pgsql-bugs >> Thread
2025-04-22 14:00:51 | RE: Disabled logical replication origin session causes primary key errors (Hayato Kuroda (Fujitsu))
valid value, but yes it is not mandatory. I intentionally used poll_query_until(), but I have
Mailing lists >> pgsql-bugs >> Thread
2025-04-10 21:17:17 | Re: BUG #18888: /src/interfaces/ecpg/preproc/descriptor.c possible NULL dereference (Euler Taveira)
valid pointer. If you're directly opening bug reports based on a static analyzer output
Mailing lists >> pgsql-bugs >> Thread
2025-03-25 13:08:23 | BUG #18865: pg_resetwal error: multitransaction offset (-O) must not be -1 (PG Bug reporting form)
valid within two weeks) 001-bad - it is a result with orignal postgres (master, PG18
Mailing lists >> pgsql-bugs >> Thread
2025-03-24 21:35:07 | BUG #18863: Multixact wraparound and pg_resetwal error "multitransaction ID (-m) must not be 0 (PG Bug reporting form)
valid within two weeks) 001-bad - it is a result with orignal postgres (master, PG18
Mailing lists >> pgsql-bugs >> Thread
2025-03-20 04:11:33 | 回复：Re: The != and +/- signs are joined together as an operator (谭忠涛)
valid operator names that do not exist so “operator not found” is the > correct
Mailing lists >> pgsql-bugs >> Thread
2025-03-19 18:45:20 | Re: Possible bug acldefault function (Tom Lane)
valid input, because materialized views are not a distinct kind of object for ACL purposes
Mailing lists >> pgsql-bugs >> Thread
2025-03-19 17:07:17 | Re: The != and +/- signs are joined together as an operator (David G. Johnston)
valid operator names that do not exist so “operator not found” is the correct outcome
Mailing lists >> pgsql-bugs >> Thread
2025-03-14 19:08:36 | Re: ISN extension - wrong volatility level for isn_weak() function (Viktor Holmberg)
valid I think it’s actually quite nice. A GUC variable would be very nice
Mailing lists >> pgsql-bugs >> Thread
2025-03-14 16:50:57 | BUG #18847: Different Query Results with and without a Primary Key Constraint (David G. Johnston)
valid version to be reporting bugs against or asking for support on. Or to be running
Mailing lists >> pgsql-bugs >> Thread >> Search in thread (2)
2025-03-14 16:48:35 | Re: BUG #18846: Incorrect Filtering Behavior with FULL OUTER JOIN and WHERE Condition (David G. Johnston)
valid version to be reporting bugs against or asking for support on. Or to be running