Repository navigation
refactor: create extension from beginning of lineage - #304
AndrewJackson2020 wants to merge 2 commits into
Conversation
|
objects match between branches, diffed in vim and they look the same this PR master |
|
Also diffed the pg_dump (after dropping all objects form the extension) no diffs. Weird that tests are failing though. |
|
I ran the previous upgrade test incorrectly. There definitely are diffs. Seems like an upgrade was missed at some point. |
|
Agree with the direction 👍 |
37fbfdc to
1c7b517
Compare
|
Went ahead and patched one missed diff. I think it matches now. |
1c7b517 to
67ef171
Compare
|
Okay I messed up the previous diff, there is still one differential between the upgrade scripts and the snapshot sql script. One of these diffs I believe was added because the table stated out with a primary key which was dropped without removing the null constraint. I suspect the snapshot sql file is incorrect and we do in fact want this column to be non nullable. This does create issues though as now we have some of the fleet without this constant and others with it. I believe that this was introduced in 07e6314 as apart of the v0.5 release. |
|
last diff is shown below. seems like it was introduced in 8c059af. pg_net.sql was updated but not the corresponding upgrade script for the v0.7.1 release.vk/ master and in this commit |
a6421a0 to
5eaf0f6
Compare
hanefi
left a comment
There was a problem hiding this comment.
Looks good overall. However I do not feel confident to approve it and would like another set of eyes to take a look.
|
Nitpick: looks like this should be a |
55a2fb6 to
6aebc3d
Compare
Currently in pg_net the upgrade code path is different from the create extension code path. When running tests internally we are not able to do true upgrade testing because the initial release of pg_net, 0.1 is not avaiable. This commit cherry picks 0.1 from the 0.1 tag, removes the pg_net.sql file and forces all create extension to happen by creating 0.1 and upgrading all the way until the current version. This commit also corrects a missing migration that was added pg_net.sql but not in the uprade script during 8b55e96. Regarding this missing migraiton, this may need an additional PR to correct somehow. It is not hard to imagine instances in the wild that do not have this modified function that should. I think this is a better approach and will open us up for upgrade testing internal to the repo. This commit
6aebc3d to
00ff5c2
Compare
Changed. Though I will say that this refactor exposed some inconsistencies. |
Currently in pg_net the upgrade code path is different from the create extension code path. When running tests internally we are not able to do true upgrade testing because the initial release of pg_net, 0.1 is not avaiable. This commit cherry picks 0.1 from the 0.1 tag, removes the pg_net.sql file and forces all create extension to happen by creating 0.1 and upgrading all the way until the current version. I think this is a better approach and will open us up for upgrade testing internal to the repo.