postgresql - Postgres ignores indexes after upgrade to 9.5 -


we have upgraded our oltp production db (2tb) v9.2.9.21 9.5.1.6 using pg_upgrade.

the upgrade went without incident , have been running week, have found optimizer ignoring indexes on 2 of our largest partitioned tables. (note: different issue 38943115, data migrated no issues).

the tables constructed individual btree indexes on bigint columns, optimizer return queries on sub-second. post-upgrade queries take 16 minutes (unusable our customers). partitions <100gb, 2-3 partitions per table.

we suspected index corruption , tried adding duplicate indexes , analyzing, new indexes still ignored unless force using enable_seqscan=no or reduce random_page_cost 2 (not practical system-wide). query response times using new indexes still appalling (16 minutes).

we have tried increasing effective_cache_size no effect. db 24x7 cannot reindex tables/ partitions.

the indexes defined so:

create index table1_column1_index on table1 using btree (column1); create index table1part1_column1_index on table1 using btree (column1); create index table1part2_column1_index on table1 using btree (column1); create index table1part3_column1_index on table1 using btree (column1);

....and repeats each subsequent column in query (the query plan isn't using composite indexes).

has encountered or suggest further steps?


Comments

Post a Comment

Popular posts from this blog

Ansible warning on jinja2 braces on when -

i using code in vars my_var: "{{lookup('env','my_var') | default(true, true)}}" i using like - include: task.yml when: my_var this worked without issue in ansible 2.2 in ansible 2.3 warning this [warning]: when statements should not include jinja2 templating delimiters such {{ }} or {% %}. found: {{lookup('env','my_var') | default(true, true)}} so if use my_var: "lookup('env','my_var') | default(true, true)" , mean remove {{ }} , no warning my_var evaluated true no matter if pass false env variable. works fine in previous code gave how can fix it? the cleanest way set fact instead of using template in variable (it prevent lookup plugin being called multiple times in included tasks - not huge performance gain, cleaner): - set_fact: my_var: "{{lookup('env','my_var') | default(true, true)}}" also mind evaluate true in cases when environment my_var diff...
Read more

Parsing a protocol message from Go by Java -

i write server(go)-client(java) programe, , use protobuf communication. define proto file , share between server , client. in server side: compile shared proto file go protoc serialize object proto.marshal send client make request service in client side: compile shared proto file java protoc get bytes transferred via http deserialize bytes object. here following error: "com.google.protobuf.invalidprotocolbufferexception: while parsing protocol message, input ended unexpectedly in middle of field. mean either input has been truncated or embedded message misreported own length." i confirmed http work fine , value of bytes received in client side same bytes send server. have same problem on this? here proto file syntax = "proto3"; package tutorial; message person { string name = 1; int32 id = 2; string email = 3; enum phonetype { mobile = 0; home = 1; work = 2; } message phonenumber { ...
Read more

node.js - Node js - Trying to send POST request, but it is not loading javascript content -

i have been trying send post request website, , has not been loading full site. i guessing problem node js not loading javascript content, executing it. can see javascript in response, though never loads content javascript files producing in html. what mean is, doesn't execute javascript. how make node js code overcome this, , wait the full website load? have tried native code, , "request' module, both producing same errors. if helps, don't need native javascript. modules fine. some code have tried (request module): var options = { method: 'post', uri: 'https://url', formdata: { 'email': 'email', 'prize': '0', 'transactional': 'on' }, headers: { /* 'content-type': 'application/x-www-form-urlencoded' */ // set automatically } }; rp(options) .then(function (body) { console.log(body) }) .catch(function (err) { console.log(err) }); when fetch content...
Read more