easy resetting - Search results in mailing lists
Mailing lists >> pgsql-bugs >> Thread
2025-07-02 22:21:50 | Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in (Tom Lane)
easy to reproduce this crash by modifying the postgres_fdw regression tests, along the lines of diff --git a/contrib/postgres_fdw/sql/postgres_fdw.sql b/contrib/postgres_fdw/sql/postgres_fdw.sql index e534b40de3c..883dc669deb 100644 --- a/contrib/postgres_fdw/sql/postgres_fdw.sql +++ b/contrib/postgres_fdw/sql/postgres_fdw.sql @@ -8,7 +8,7 @@ CREATE SERVER testserver1 FOREIGN DATA
Mailing lists >> pgsql-bugs >> Thread
2025-06-12 02:46:26 | Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements (Michael Paquier)
setting the location and length to not include the first parenthesis, like that. I have to admit that it is inconsistent to set a location in their respective inner nodes while
Mailing lists >> pgsql-bugs >> Thread
2025-04-24 11:40:42 | Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c" (Richard Guo)
setting outersortkeys (resp. innersortkeys) to NIL. This reflects a basic assumption: if MergePath.outersortkeys is not NIL, it means the outer path is not sufficiently ordered. Therefore, I think the "Assert(!is_sorted)" when outersortkeys
Mailing lists >> pgsql-bugs >> Thread
2025-04-22 23:53:23 | Re: Command order bug in pg_dump (Tom Lane)
easy to get ChooseConstraintName to do something just slightly different from what I said above: the rule is now "add an underscore and some digits to the name used for the parent constraint". I like
Mailing lists >> pgsql-bugs >> Thread
2024-12-06 21:44:24 | Re: BUG #18735: Specific multibyte character in psql file path command parameter for Windows (Tom Lane)
easy enough to make that loop (and the similar one in cleanup_path) encoding-aware, if we knew what encoding applies. Deciding that is the sticky part. After sleeping on it, I'm coming around
Mailing lists >> pgsql-bugs >> Thread
2024-11-22 22:23:47 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now (Tom Lane)
settings(Oid databaseid, Oid roleid); * descriptors for both pg_database and its indexes from the shared relcache * cache file, and so we can do an indexscan. criticalSharedRelcachesBuilt * tells whether we got the cached descriptors. + * + * This
Mailing lists >> pgsql-bugs >> Thread
2024-09-05 00:09:16 | Re: BUG #18599: server closed the connection unexpectedly (Thomas Munro)
setting "jit=off" fixes it, then it could be the known LLVM relocation issue[1], for which we have a candidate solution pending. I mention this wild guess because we're seeing
Mailing lists >> pgsql-bugs >> Thread
2024-02-08 05:54:52 | Re: Potential data loss due to race condition during logical replication slot creation (Masahiko Sawada)
setter function for in_create. There are several ideas where to set/reset the flag. One idea is that we reset the flag in AllocateSnapshotBuilder() and set the flag anywhere before starting to find the start
Mailing lists >> pgsql-bugs >> Thread
2024-01-18 06:52:12 | Re: [16+] subscription can end up in inconsistent state (vignesh C)
setting the hba for this user too and removing the trust for all users. We need to remove the trust from all users as otherwise we will hit "Non-superuser cannot connect if the server
Mailing lists >> pgsql-bugs >> Thread
2023-11-07 17:41:38 | Segfault when running postgres inside kubernetes with huge pages (Siegfried Kiermayer)
setting on the node itself. I would go into more detail but honestly I believe this might be easy
Mailing lists >> pgsql-bugs >> Thread
2023-10-24 09:48:06 | Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx (Amit Langote)
easiest fix to me (attached PoC makes the error go away for me and passes check-world). By setting
Mailing lists >> pgsql-bugs >> Thread
2023-07-10 23:52:23 | Re: BUG #18009: Postgres Recovery not happening (Thomas Munro)
setting is called "debug_io_direct", with a temporary "debug_" prefix because we don't want people turning it on for real production databases yet. But that's the easy
Mailing lists >> pgsql-bugs >> Thread
2023-06-14 21:37:24 | Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon (Andres Freund)
setting up MyProc->databaseId, I think. Otherwise a concurrent vacuum could decide to remove database contents we think we still can see. If we had something like that it should be fairly easy
Mailing lists >> pgsql-bugs >> Thread
2023-03-15 09:08:18 | BUG #17844: Memory consumption for memoize node (PG Bug reporting form)
settings to trigger plan with memoize node set work_mem = '128MB'; set enable_hashjoin = off; set enable_mergejoin = off; set jit = off; explain (analyze, buffers) select test_json.id, test_json2.id from test_json
Mailing lists >> pgsql-bugs >> Thread
2023-02-13 06:45:49 | Re: WAL segments removed from primary despite the fact that logical replication slot needs it (Kyotaro Horiguchi)
easy to do that, but that log is highly accompanied by a LOG line "terminating process %d to release replication slot \"%s\"". I don't mind adding it if it is a DEBUGx. I think