Project

General

Profile

Feature #2808

allow database scans for unused primary keys to be disabled in SequenceIdentityManager

Added by Eric Faulhaber over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Eric Faulhaber
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
version_reported:
version_resolved:

History

#1 Updated by Eric Faulhaber over 8 years ago

Add an optional setting to the directory that would be read in SequenceIdentityManager.setIdentityPool, to disable scanning for unused primary keys. The default will be for scanning to be enabled. This setting would override.

#2 Updated by Paul E over 8 years ago

The sooner this is done the higher it's value for us.

At the moment the postgres bug that the PK scan triggers is rendering our test pipeline useless.
Within the next week we hopefully won't need this setting any more, assuming we don't trigger the bug in postgres 9.4.

Can you please let me know when this change is likely to be made as knowing will influence my immediate priorities?

#3 Updated by Eric Faulhaber over 8 years ago

I am in the middle of a fairly big, unrelated change. I can piggy-back this feature onto that change when it goes into testing, hopefully later this week.

#4 Updated by Paul E over 8 years ago

Ok, thanks Eric.

#5 Updated by Eric Faulhaber over 8 years ago

  • Status changed from New to Closed
  • Assignee set to Eric Faulhaber

Paul, sorry, I should have seen this earlier; turns out this feature has been there all along, but it had long since left my memory. Just set the following in your directory instead of the other changes you made:

<node class="container" name="identity_pool">
  <node class="string" name="scan_method">
    <node-attribute name="value" value="NONE"/>
  </node>
</node>

#6 Updated by Paul E over 8 years ago

Eric, no need to apologise - I should have noticed this myself.

Thanks!

Also available in: Atom PDF