Postgres triggers and no-op updates
On Postgres 9.5 I've implemented an eager materialised view with upsert triggers on UPDATE (I need incremental updating, and the built-in materialised views don't support that), this seems to work well.
But I also have the need to initialise these tables on existing DBs, and sometimes to truncate and rebuild them; I need the built-in REFRESH MATERIALIZED VTEW. I could duplicate the upsert queries in the triggers, modifying the trigger-specific code, but I don't like duplicate code.
I find that running a no-op UPDATE on the trigger's source table(s)
UPDATE source_table SET id = id;
does trigger my triggers, and so updates the view as required.
I've not come across this sort of "touch" query before, and worry that that it might be fragile -- Postgres happens to behave like this now, but it's not standard and will change in 9.6. A justified worry?
postgresql triggers materialized-views
asked Nov 21 '18 at 0:04
jjg
201210
add a comment |
On Postgres 9.5 I've implemented an eager materialised view with upsert triggers on UPDATE (I need incremental updating, and the built-in materialised views don't support that), this seems to work well.
But I also have the need to initialise these tables on existing DBs, and sometimes to truncate and rebuild them; I need the built-in REFRESH MATERIALIZED VTEW. I could duplicate the upsert queries in the triggers, modifying the trigger-specific code, but I don't like duplicate code.
I find that running a no-op UPDATE on the trigger's source table(s)
UPDATE source_table SET id = id;
does trigger my triggers, and so updates the view as required.
I've not come across this sort of "touch" query before, and worry that that it might be fragile -- Postgres happens to behave like this now, but it's not standard and will change in 9.6. A justified worry?
postgresql triggers materialized-views
asked Nov 21 '18 at 0:04
jjg
201210
1
This idle update in no way differs from any other real update. It doesn't depend on the Postgres version and doesn't seem it would change in future.
– klin
Nov 21 '18 at 0:58
The behavior won't change precisely because that would break use cases like this.
– Laurenz Albe
Nov 21 '18 at 4:52
add a comment |
On Postgres 9.5 I've implemented an eager materialised view with upsert triggers on UPDATE (I need incremental updating, and the built-in materialised views don't support that), this seems to work well.
But I also have the need to initialise these tables on existing DBs, and sometimes to truncate and rebuild them; I need the built-in REFRESH MATERIALIZED VTEW. I could duplicate the upsert queries in the triggers, modifying the trigger-specific code, but I don't like duplicate code.
I find that running a no-op UPDATE on the trigger's source table(s)
UPDATE source_table SET id = id;
does trigger my triggers, and so updates the view as required.
I've not come across this sort of "touch" query before, and worry that that it might be fragile -- Postgres happens to behave like this now, but it's not standard and will change in 9.6. A justified worry?
postgresql triggers materialized-views
asked Nov 21 '18 at 0:04
jjg
201210
On Postgres 9.5 I've implemented an eager materialised view with upsert triggers on UPDATE (I need incremental updating, and the built-in materialised views don't support that), this seems to work well.
But I also have the need to initialise these tables on existing DBs, and sometimes to truncate and rebuild them; I need the built-in REFRESH MATERIALIZED VTEW. I could duplicate the upsert queries in the triggers, modifying the trigger-specific code, but I don't like duplicate code.
I find that running a no-op UPDATE on the trigger's source table(s)
UPDATE source_table SET id = id;
does trigger my triggers, and so updates the view as required.
I've not come across this sort of "touch" query before, and worry that that it might be fragile -- Postgres happens to behave like this now, but it's not standard and will change in 9.6. A justified worry?
postgresql triggers materialized-views
postgresql triggers materialized-views
asked Nov 21 '18 at 0:04
jjg
201210
asked Nov 21 '18 at 0:04
jjg
201210
asked Nov 21 '18 at 0:04
jjg
201210
asked Nov 21 '18 at 0:04
jjg
201210
asked Nov 21 '18 at 0:04
jjg
201210
201210
1
This idle update in no way differs from any other real update. It doesn't depend on the Postgres version and doesn't seem it would change in future.
– klin
Nov 21 '18 at 0:58
The behavior won't change precisely because that would break use cases like this.
– Laurenz Albe
Nov 21 '18 at 4:52
add a comment |
1
This idle update in no way differs from any other real update. It doesn't depend on the Postgres version and doesn't seem it would change in future.
– klin
Nov 21 '18 at 0:58
The behavior won't change precisely because that would break use cases like this.
– Laurenz Albe
Nov 21 '18 at 4:52
1
1
This idle update in no way differs from any other real update. It doesn't depend on the Postgres version and doesn't seem it would change in future.
– klin
Nov 21 '18 at 0:58
This idle update in no way differs from any other real update. It doesn't depend on the Postgres version and doesn't seem it would change in future.
– klin
Nov 21 '18 at 0:58
The behavior won't change precisely because that would break use cases like this.
– Laurenz Albe
Nov 21 '18 at 4:52
The behavior won't change precisely because that would break use cases like this.
– Laurenz Albe
Nov 21 '18 at 4:52
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53403464%2fpostgres-triggers-and-no-op-updates%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53403464%2fpostgres-triggers-and-no-op-updates%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
This idle update in no way differs from any other real update. It doesn't depend on the Postgres version and doesn't seem it would change in future.
– klin
Nov 21 '18 at 0:58
The behavior won't change precisely because that would break use cases like this.
– Laurenz Albe
Nov 21 '18 at 4:52