Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider increasing the sequence allocationSize #884

Open
banterCZ opened this issue Apr 13, 2023 · 1 comment
Open

Consider increasing the sequence allocationSize #884

banterCZ opened this issue Apr 13, 2023 · 1 comment

Comments

@banterCZ
Copy link
Member

Look into increasing the allocationSize for generated identifiers using DB sequences.

Due to upgrading to Hibernate 6 set to

 @Id
 @SequenceGenerator(name = "pa_master_keypair", sequenceName = "pa_master_keypair_seq", allocationSize = 1)
 @GeneratedValue(strategy = GenerationType.AUTO, generator = "pa_master_keypair")
 @Column(name = "id")
 private Long id;

This is compatible with the current sequences but could be improved to take advantage of hi-lo algorithms.

Follow-up to #869

@petrdvorak
Copy link
Member

petrdvorak commented Apr 18, 2023

This has a very low priority. We keep one master keypair per application. This means that most customers only have one record in the table. Also - and I know this is a very old issue - we might actually adjust the PAS model to promote keypair rotation with a version upgrade, see: #691.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants