![]() ![]() While trying to call an aggregate function failed already, calling a window function would crash, and calling a procedure would work only if the procedure did no transaction control.Įxtend pg_identify_object_as_address() to support event triggers (Joel Jacobson)įix to_char()'s handling of Roman-numeral month format codes with negative intervals (Julien Rouhaud) This could cause crashes in some situations.ĭisallow calling window functions and procedures via the “ fast path” wire protocol message (Tom Lane) ![]() While that normally has no real impact (since COLLATE has no effect at runtime), it was possible to construct views that would be rejected during dump/reload.įix use-after-free bug in saving tuples for AFTER triggers (Amit Langote) This led to a parse tree in which the COLLATE appears to be applied to a non-collatable value. Sufficiently deep nesting of WITH constructs (at least seven levels) triggered core dumps or incorrect complaints of faulty WITH nesting.įix bug with coercing the result of a COLLATE expression to a non-collatable type (Tom Lane) This created a command ordering hazard for dump/reload and upgrade scenarios.Įnsure that REINDEX CONCURRENTLY preserves any statistics target that's been set for the index (Michael Paquier)įix COMMIT AND CHAIN to work correctly when the current transaction has live savepoints (Fujii Masao)įix list-manipulation bug in WITH RECURSIVE processing (Michael Paquier, Tom Lane) Previously, over-eager validity checks might reject these commands, even if the values would have worked when used later. SET to set the role, session_authorization, and temp_buffers parameters (Tom Lane) AS IDENTITY implies NOT NULL, so don't allow it to be combined with an explicit NULL specification.Īllow ALTER ROLE/DATABASE. INHERIT, insist that any generated columns in the parent be generated the same way in the child (Peter Eisentraut)įorbid marking an identity column as nullable (Vik Fearing) When attaching a child table with ALTER TABLE. The only supported case is for the whole partitioning hierarchy to have identical constraint properties, so such ALTERs must be applied at the partition root. This change also disallows applying such an ALTER directly to the constraints of leaf partitions. After updating to this version, any misbehaving partitioned tables can be fixed by executing a new ALTER command to set the desired properties. This led to unexpected behavior of such constraints. ALTER CONSTRAINT failed to adjust the DEFERRABLE and/or INITIALLY DEFERRED markings of the constraints and triggers of leaf partitions. When applied to a foreign-key constraint of a partitioned table, ALTER TABLE. (CVE-2021-32029)įix adjustment of constraint deferrability properties in partitioned tables (Álvaro Herrera) No error is observed unless the UPDATE involves other tables being joined to the target table. If an UPDATE for a partitioned table caused a row to be moved to another partition with a physically different row type (for example, one with a different set of dropped columns), computation of RETURNING results for that row could produce errors or wrong answers. RETURNING outputs for joined cross-partition updates (Amit Langote, Etsuro Fujita) (CVE-2021-32028)įix possibly-incorrect computation of UPDATE. In addition, in versions supporting cross-partition updates, a cross-partition update triggered by such a case had the reverse problem: the junk columns were removed from the target list, typically causing an immediate crash due to malfunction of the multi-column sub-select mechanism. That's fairly harmless in the short run, but if new columns are added to the table then the values would become accessible, possibly leading to malfunctions if they don't match the datatypes of the added columns. If the UPDATE list contains any multi-column sub-selects (which give rise to junk columns in addition to the results proper), the UPDATE path would end up storing tuples that include the values of the extra junk columns. (CVE-2021-32027)įix mishandling of “ junk” columns in INSERT. This could lead to memory overwrites, with ensuing crashes or unwanted data modifications. This resulted in later entries in the array becoming inaccessible (since their subscripts could not be written as integers), but more importantly it confused subsequent assignment operations. ![]() The array code previously did not complain about cases where an array's lower bound plus length overflows an integer. Prevent integer overflows in array subscripting calculations (Tom Lane)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |