Mailing lists [pgsql-bugs]
- Duplicate Workers entries in some EXPLAIN plans Maciek Sakrejda
- Re: BUG #16060: JDBC - badly gets DateOffsetTime value from database Michael Paquier
- Re: BUG #16058: show session_user shows a not clear error message Michael Paquier
- Re: BUG #16060: JDBC - badly gets DateOffsetTime value from database Dave Cramer
- Re: ERROR: multixact X from before cutoff Y found to be still running Thomas Munro
- Re: ERROR: multixact X from before cutoff Y found to be still running Thomas Munro
- Re: Re: BUG #15929: logical decoding can not write down the analyse result when the output file is touched. movead.li@highgo.ca
- Re: Duplicate Workers entries in some EXPLAIN plans Tom Lane
- Re: Duplicate Workers entries in some EXPLAIN plans Maciek Sakrejda
- BUG #16061: pgadmin PG Bug reporting form
- Re: BUG #16060: JDBC - badly gets DateOffsetTime value from database stan@marencik.cz
- Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
- Re: BUG #16049: log_line_prefix=%a and log_connections -application_name missing death lock
- Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
- Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12 Tom Lane
- Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
- Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12 Tomas Vondra
- pg_restore creates duplicate records when used with --roleparameter Ivan Pantić
- Re: ERROR: multixact X from before cutoff Y found to be still running Bossart, Nathan
- Re: ERROR: multixact X from before cutoff Y found to be still running Bossart, Nathan
- Re: ERROR: multixact X from before cutoff Y found to be still running Jeremy Schneider
- Re: ERROR: multixact X from before cutoff Y found to be still running Jeremy Schneider