Bug in plpgsql, when using NEW with composite field value. - Mailing list pgsql-bugs

From Oleg Serov
Subject Bug in plpgsql, when using NEW with composite field value.
Date
Msg-id cec7c6df0812100154h21cd6117sfb98fafb8643c896@mail.gmail.com
Whole thread Raw
Responses Re: Bug in plpgsql, when using NEW with composite field value.  ("Pavel Stehule" <pavel.stehule@gmail.com>)
Re: Bug in plpgsql, when using NEW with composite field value.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
U1FMOgoKQ1JFQVRFIE9SIFJFUExBQ0UgRlVOQ1RJT04gImJ1Z193aXRoX3Ry
aWdnZXJzIiAoKSBSRVRVUk5TIHRyaWdnZXIgQVMKJGJvZHkkCkJFR0lOCglQ
RVJGT1JNIENPQUxFU0NFKE5FVy5zb21lX2NvbXBvc2l0ZV9maWVsZC5maWVs
ZCwgVFJVRSk7CkVORDsKJGJvZHkkCkxBTkdVQUdFICdwbHBnc3FsJyBWT0xB
VElMRSBDQUxMRUQgT04gTlVMTCBJTlBVVCBTRUNVUklUWSBJTlZPS0VSOwoK
RXJyb3I6CgpFUlJPUjogIE5FVyB1c2VkIGluIHF1ZXJ5IHRoYXQgaXMgbm90
IGluIGEgcnVsZQpRVUVSWTogIFNFTEVDVCAgQ09BTEVTQ0UoTkVXLnNvbWVj
b21wb3NpdGVmaWVsZC5maWVsZCwgVFJVRSkKQ09OVEVYVDogIFNRTCBzdGF0
ZW1lbnQgaW4gUEwvUGdTUUwgZnVuY3Rpb24gImJ1Z193aXRoX3RyaWdnZXJz
IiBuZWFyIGxpbmUgMgoKCioqKioqKioqKiogRVJST1IgKioqKioqKioqKgoK
RVJST1I6IE5FVyB1c2VkIGluIHF1ZXJ5IHRoYXQgaXMgbm90IGluIGEgcnVs
ZQpTUUwgc3RhdGU6IDQyNjAxCuvPztTFy9PUOlNRTCBzdGF0ZW1lbnQgaW4g
UEwvUGdTUUwgZnVuY3Rpb24gImJ1Z193aXRoX3RyaWdnZXJzIiBuZWFyIGxp
bmUgMgo=

pgsql-bugs by date:

Previous
From: Marc Schablewski
Date:
Subject: Re: BUG #4565: nextval not updated during wal replication, leading to pk violations
Next
From: "Oleg Serov"
Date:
Subject: plpgsql bug OR future request: Assign fileds in composite subfiled. eg. table.compositefield.subfield := TRUE;