Postgres Pro
Downloads
Home   >   mailing lists

BUG #14439: Trigger function fails with internal error after upgrade to 9.6 - Mailing list pgsql-bugs

From max.valjanski@gmail.com
Subject BUG #14439: Trigger function fails with internal error after upgrade to 9.6
Date
Msg-id 20161129141639.6530.37563@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #14439: Trigger function fails with internal error after upgrade to 9.6
Re: BUG #14439: Trigger function fails with internal error after upgrade to 9.6
List pgsql-bugs
Tree view 
VGhlIGZvbGxvd2luZyBidWcgaGFzIGJlZW4gbG9nZ2VkIG9uIHRoZSB3ZWJz
aXRlOgoKQnVnIHJlZmVyZW5jZTogICAgICAxNDQzOQpMb2dnZWQgYnk6ICAg
ICAgICAgIE1heGltIFZhbHlhbnNraXkKRW1haWwgYWRkcmVzczogICAgICBt
YXgudmFsamFuc2tpQGdtYWlsLmNvbQpQb3N0Z3JlU1FMIHZlcnNpb246IDku
Ni4xCk9wZXJhdGluZyBzeXN0ZW06ICAgQ2VudE9TIDYuOApEZXNjcmlwdGlv
bjogICAgICAgIAoKVHJpZ2dlciBmdW5jdGlvbiBzdG9wcGVkIHdvcmtpbmcg
YWZ0ZXIgdXBncmFkZSBmcm9tIDkuNSB0byA5LjYuIFVwZ3JhZGUgd2FzCnBl
cmZvcm1lZCB2aWEgcGdfdXBncmFkZS4NCg0KVGhpcyBpcyB0aGF0IGVycm9y
IG91dHB1dDoNCg0KIyB1cGRhdGUgYWJfZ3JvdXAgc2V0IG5hbWU9J0RvbWFp
biBDb250cm9sbGVyeicgd2hlcmUgaWQ9NDY2Ow0KRVJST1I6ICB0YWJsZSBy
b3cgdHlwZSBhbmQgcXVlcnktc3BlY2lmaWVkIHJvdyB0eXBlIGRvIG5vdCBt
YXRjaA0K0J/QntCU0KDQntCR0J3QntCh0KLQmDogIFF1ZXJ5IHByb3ZpZGVz
IGEgdmFsdWUgZm9yIGEgZHJvcHBlZCBjb2x1bW4gYXQgb3JkaW5hbApwb3Np
dGlvbiA2Lg0K0JrQntCd0KLQldCa0KHQojogIFNRTCBzdGF0ZW1lbnQgIlVQ
REFURSBhYl9ncm91cCBTRVQgbmFtZV9naW4gPQp0b190c3ZlY3Rvcignc2lt
cGxlJywgTkVXLm5hbWUpIFdIRVJFIGlkID0gTkVXLmlkIEFORCBORVcubmFt
ZSA8PgpPTEQubmFtZSINClBML3BnU1FMIGZ1bmN0aW9uIHVwZGF0ZV9ncm91
cF9uYW1lX2dpbigpIGxpbmUgNCBhdCBTUUwgc3RhdGVtZW50DQoNCkkgdHJp
ZWQgdG8gcmVjcmVhdGUgZnVuY3Rpb24sIG1hZGUgVkFDVVVNIEZVTEwgYW5k
IENMVVNURVIgZm9yIHRoYXQgdGFibGUKYW5kIGl0IGRpZCBub3QgZml4IHRo
ZSBwcm9ibGVtLg0KDQpIZXJlIGlzIHNvdXJjZSBjb2RlIGZvciB0aGF0IGZ1
bmN0aW9uOg0KDQpDUkVBVEUgT1IgUkVQTEFDRSBGVU5DVElPTiBwdWJsaWMu
dXBkYXRlX2dyb3VwX25hbWVfZ2luKCkNCiBSRVRVUk5TIHRyaWdnZXINCiBM
QU5HVUFHRSBwbHBnc3FsDQpBUyAkZnVuY3Rpb24kDQogICAgICAgICAgICBC
RUdJTg0KICAgICAgICAgICAgICAgIElGIChUR19PUCA9ICdVUERBVEUnKSBU
SEVODQogICAgICAgICAgICAgICAgICAgIFVQREFURSBhYl9ncm91cCBTRVQg
bmFtZV9naW4gPSB0b190c3ZlY3Rvcignc2ltcGxlJywKTkVXLm5hbWUpIFdI
RVJFIGlkID0gTkVXLmlkIEFORCBORVcubmFtZSA8PiBPTEQubmFtZTsNCiAg
ICAgICAgICAgICAgICAgICAgUkVUVVJOIE5FVzsNCiAgICAgICAgICAgICAg
ICBFTFNJRiAoVEdfT1AgPSAnSU5TRVJUJykgVEhFTg0KICAgICAgICAgICAg
ICAgICAgICBVUERBVEUgYWJfZ3JvdXAgU0VUIG5hbWVfZ2luID0gdG9fdHN2
ZWN0b3IoJ3NpbXBsZScsCk5FVy5uYW1lKSBXSEVSRSBpZCA9IE5FVy5pZDsN
CiAgICAgICAgICAgICAgICBFTkQgSUY7DQogICAgICAgICAgICAgICAgUkVU
VVJOIE5VTEw7DQogICAgICAgICAgICBFTkQ7DQogICAgICAgICRmdW5jdGlv
biQNCiAKCg==

pgsql-bugs by date:

Previous
From: nikolay.nikitin@infowatch.com
Date:
Subject: BUG #14438: Wrong row count in the join plan with unique index scan
Next
From: Michael Day
Date:
Subject: parallel sequential scan returns extraneous rows