![]() Statistics inquiries issued within half a second of the previous postmaster shutdown were effectively ignored.Įnsure that the statistics collector's receive buffer size is at least 100KB (Tom Lane) This fix prevents reconnection failures with ticket-aware client-side SSL code.įix code for setting tcp_keepalives_idle on Solaris (Tom Lane)įix statistics collector to honor inquiry messages issued just after a postmaster shutdown and immediate restart (Tom Lane) Prevent sending SSL session tickets to clients (Tom Lane) This is expected to fix infrequent child-process-launch failures that are probably due to interference from antivirus products.įix low-probability corruption of shared predicate-lock hash table in Windows builds (Thomas Munro, Tom Lane)Īvoid logging clean closure of an SSL connection as though it were a connection reset (Michael Paquier) On Windows, retry process creation if we fail to reserve the address range for our shared memory in the new process (Tom Lane, Amit Kapila) This had consequences such as foreign-key checks failing to see a tuple that definitely exists but is being updated concurrently.įix potential data corruption when freezing a tuple whose XMAX is a multixact with exactly one still-interesting member (Teodor Sigaev)Īvoid integer overflow and ensuing crash when sorting more than one billion tuples in-memory (Sergey Koposov) If several sessions concurrently lock a tuple update chain with nonconflicting lock modes using an old snapshot, and they all succeed, it was possible for some of them to nonetheless fail (and conclude there is no live tuple version) due to a race condition. This sequence is unsafe.įix concurrent locking of tuple update chains (Álvaro Herrera) The previous documentation instructed users to start/stop the primary server after running pg_upgrade but before syncing the standby servers. (CVE-2017-7548)Ĭorrect the documentation about the process for upgrading standby servers with pg_upgrade (Bruce Momjian) Lo_put() should surely require the same permissions as lowrite(), but the check was missing, allowing any user to change the data in a large object. Make lo_put() check for UPDATE privilege on the target large object (Tom Lane, Michael Paquier) Change the server to reject empty passwords in all cases. In particular the most common method, md5, accepted empty passwords. However, with a modified or non- libpq-based client, logging in could be possible, depending on which authentication method is configured. An administrator might therefore believe that setting the password to empty is equivalent to disabling password login. So, if a user's password has been set to the empty string, it's impossible to log in with that password via psql or other libpq-based clients. Libpq ignores empty password specifications, and does not transmit them to the server. UPDATE pg_database SET datallowconn = false WHERE datname = 'template0' įinally, remove the allow_system_table_mods configuration setting, and again restart the postmaster.ĭisallow empty passwords in all password-based authentication methods (Heikki Linnakangas) ![]() In prior versions, instead use UPDATE pg_database SET datallowconn = true WHERE datname = 'template0' In PostgreSQL 9.5 and later, you can use ALTER DATABASE template0 WITH ALLOW_CONNECTIONS true Īnd then after fixing template0, undo that with ALTER DATABASE template0 WITH ALLOW_CONNECTIONS false To fix template0, you'll need to temporarily make it accept connections. Pg_foreign_server S ON (U.umserver = S.oid) ĭo not forget to include the template0 and template1 databases, or the vulnerability will still exist in databases you create later. LEFT JOIN pg_authid A ON (A.oid = U.umuser) JOIN OR (SELECT rolsuper FROM pg_authid WHERE rolname = current_user) OR (U.umuser = 0 AND pg_has_role(S.srvowner, 'USAGE')) OR has_server_privilege(S.oid, 'USAGE'))) In each database of the cluster, run the following commands as superuser: SET search_path = pg_catalog ĬREATE OR REPLACE VIEW pg_user_mappings ASĬASE WHEN (U.umuser 0 AND A.rolname = current_user (In versions supporting ALTER SYSTEM, you can use that to make the configuration change, but you'll still need a restart.) Restart the postmaster after adding allow_system_table_mods = true to nf.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |