You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Michael Paquier 55f4802785 Prevent write operations on large objects in read-only transactions ... Attempting such an operation would already fail, but in various and confusing ways. For example, while in recovery, some elog() messages would be reported, but these should never be user-facing. This commit restricts any write operations done on large objects in a read-only context, so as the errors generated are more user-friendly. This is per the discussion done with Tom Lane and Robert Haas. Some regression tests are added to check the case of all the SQL functions working on large objects (including an update of the test's alternate output). Author: Yugo Nagata Discussion: https://postgr.es/m/20220527153028.61a4608f66abcd026fd3806f@sraoss.co.jp		3 years ago
..
src	Prevent write operations on large objects in read-only transactions	3 years ago
KNOWN_BUGS	…
MISSING_FEATURES	…
Makefile	…
TODO	Change documentation references to PG website to use https: not http:	8 years ago