diff options
| author | Michael Paquier | 2012-06-15 00:14:17 +0000 |
|---|---|---|
| committer | Michael Paquier | 2012-06-15 00:14:17 +0000 |
| commit | c3e01a6277f1d1d94c6d45114a710d47ddc6ece2 (patch) | |
| tree | 29f3a3ff705a42bf794cfa1bdf8b98c4d9226f38 /src | |
| parent | cd6b5d791a5fc99c8188566f1885d98164b44154 (diff) | |
Fix for sequence removal on GTM when related database is dropped
There was an error on GTM side on when comparing sequence key strings
related to key size when sequence drop is based on a sequence key type
GTM_SEQ_DB_NAME.
Here is an example that was failing:
create database test;
\c test
create sequence toto;
\c postgres
-- Sequence not dropped on GTM when database is dropped
drop database test;
create database test;
\c test
-- error cannot re-create sequence, GTM complains
-- because sequence is seen as already created on GTM
create sequence toto;
Report and test case by Dimitrije Radojevic
Diffstat (limited to 'src')
| -rw-r--r-- | src/gtm/main/gtm_seq.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/gtm/main/gtm_seq.c b/src/gtm/main/gtm_seq.c index b6a84b865b..32f4da48f3 100644 --- a/src/gtm/main/gtm_seq.c +++ b/src/gtm/main/gtm_seq.c @@ -508,11 +508,11 @@ seq_key_dbname_equal(GTM_SequenceKey nsp, GTM_SequenceKey seq) * Check also if first part of sequence key name has a dot at the right place. * This accelerates process instead of making numerous memcmp. */ - if (seq->gsk_key[nsp->gsk_keylen] != '.') + if (seq->gsk_key[nsp->gsk_keylen - 1] != '.') return false; /* Then Check the strings */ - return (memcmp(nsp->gsk_key, seq->gsk_key, nsp->gsk_keylen) == 0); + return (memcmp(nsp->gsk_key, seq->gsk_key, nsp->gsk_keylen - 1) == 0); } /* |