Обсуждение: BUG #14143: stop database with -m immediate cause fatal message log when database start
BUG #14143: stop database with -m immediate cause fatal message log when database start
От
marc47marc47@gmail.com
Дата:
VGhlIGZvbGxvd2luZyBidWcgaGFzIGJlZW4gbG9nZ2VkIG9uIHRoZSB3ZWJz aXRlOgoKQnVnIHJlZmVyZW5jZTogICAgICAxNDE0MwpMb2dnZWQgYnk6ICAg ICAgICAgIG1hcmMgaHNpYW8KRW1haWwgYWRkcmVzczogICAgICBtYXJjNDdt YXJjNDdAZ21haWwuY29tClBvc3RncmVTUUwgdmVyc2lvbjogOS42YmV0YTEK T3BlcmF0aW5nIHN5c3RlbTogICBDZW50b3MgNS40CkRlc2NyaXB0aW9uOiAg ICAgICAgCgpUaGUgZGF0YWJhc2Ugc3RhcnQgd2l0aCBGQVRBTCBtZXNzYWdl IHdoZW4gSSB0cnkgdG8gc3RvcCB0aGUgZGF0YWJhc2Ugd2l0aAppbW1lZGlh dGUuDQpJIGFzc3VtZSB0aGF0IEZBVEFMLCBpcyBhIGNyaXRpY2FsIGVycm9y IGxvZywgaXQgc2hvdWxkIGJlIGFuIHdhcm5pbmcKb25seS4NCg0KTXkgYXBw bGljYXRpb24gd2lsbCBub3QgY29udGludWUgd2hlbiBkYXRhYmFzZSBoYXMg RkFUQUwgbG9nIGluIHN0YXJ0aW5nCnByb2dyZXNzLg0KDQoNCltkYnNlY3Vy ZUByZDQgKFNlY3VDZW50ZXJfKSBTZWN1cmVDZW50ZXJdJHBnX2N0bCBzdG9w IC1tIGltbWVkaWF0ZQ0Kd2FpdGluZyBmb3Igc2VydmVyIHRvIHNodXQgZG93 bi4uLi5MT0c6ICByZWNlaXZlZCBpbW1lZGlhdGUgc2h1dGRvd24KcmVxdWVz dA0KV0FSTklORzogIHRlcm1pbmF0aW5nIGNvbm5lY3Rpb24gYmVjYXVzZSBv ZiBjcmFzaCBvZiBhbm90aGVyIHNlcnZlcgpwcm9jZXNzDQpERVRBSUw6ICBU aGUgcG9zdG1hc3RlciBoYXMgY29tbWFuZGVkIHRoaXMgc2VydmVyIHByb2Nl c3MgdG8gcm9sbCBiYWNrIHRoZQpjdXJyZW50IHRyYW5zYWN0aW9uIGFuZCBl eGl0LCBiZWNhdXNlIGFub3RoZXIgc2VydmVyIHByb2Nlc3MgZXhpdGVkCmFi bm9ybWFsbHkgYW5kIHBvc3NpYmx5IGNvcnJ1cHRlZCBzaGFyZWQgbWVtb3J5 Lg0KSElOVDogIEluIGEgbW9tZW50IHlvdSBzaG91bGQgYmUgYWJsZSB0byBy ZWNvbm5lY3QgdG8gdGhlIGRhdGFiYXNlIGFuZApyZXBlYXQgeW91ciBjb21t YW5kLg0KTE9HOiAgZGF0YWJhc2Ugc3lzdGVtIGlzIHNodXQgZG93bg0KIGRv bmUNCnNlcnZlciBzdG9wcGVkDQpbZGJzZWN1cmVAcmQ0IChTZWN1Q2VudGVy XykgU2VjdXJlQ2VudGVyXSRwZ19jdGwgLUQgLi9kYXRhIC13IHN0YXJ0DQp3 YWl0aW5nIGZvciBzZXJ2ZXIgdG8gc3RhcnQuLi4uTE9HOiAgZGF0YWJhc2Ug c3lzdGVtIHdhcyBpbnRlcnJ1cHRlZDsgbGFzdAprbm93biB1cCBhdCAyMDE2 LTA1LTE3IDEyOjAzOjA5IENTVA0KRkFUQUw6ICB0aGUgZGF0YWJhc2Ugc3lz dGVtIGlzIHN0YXJ0aW5nIHVwDQouTE9HOiAgZGF0YWJhc2Ugc3lzdGVtIHdh cyBub3QgcHJvcGVybHkgc2h1dCBkb3duOyBhdXRvbWF0aWMgcmVjb3Zlcnkg aW4KcHJvZ3Jlc3MNCkxPRzogIGludmFsaWQgcmVjb3JkIGxlbmd0aCBhdCAw LzdBNUY3NzA6IHdhbnRlZCAyNCwgZ290IDANCkxPRzogIHJlZG8gaXMgbm90 IHJlcXVpcmVkDQpMT0c6ICBNdWx0aVhhY3QgbWVtYmVyIHdyYXBhcm91bmQg cHJvdGVjdGlvbnMgYXJlIG5vdyBlbmFibGVkDQpMT0c6ICBhdXRvdmFjdXVt IGxhdW5jaGVyIHN0YXJ0ZWQNCkxPRzogIGRhdGFiYXNlIHN5c3RlbSBpcyBy ZWFkeSB0byBhY2NlcHQgY29ubmVjdGlvbnMNCiBkb25lDQpzZXJ2ZXIgc3Rh cnRlZA0KCgo=
Re: BUG #14143: stop database with -m immediate cause fatal message log when database start
От
Kevin Grittner
Дата:
On Tue, May 17, 2016 at 12:14 AM, <marc47marc47@gmail.com> wrote: > The database start with FATAL message when I try to stop the database with > immediate. That is not a bug; stop immediate forces a crash of the service, and crash recovery is needed when the service is started again. > I assume that FATAL, is a critical error log, it should be an warning > only. FATAL means the connection involved was broken. It was. More than that, though, you should pretty much never use stop immediate unless the building is on fire (literally) or you don't plan to keep the cluster after it is stopped. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company