Details
-
Type:
Enhancement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.8.0
-
Fix Version/s: Backlog
-
Component/s: Alarms/Automations/Vacuumd
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Environment:Operating System: Linux
Platform: PC
-
Bugzilla Id:3952
Description
If you want to run a function in the action of an automation, you have to run "select functionname()". This returns a result and vacuumd complains
2010-07-09 13:08:46,185 WARN [VacuumdScheduler-2 Pool-fiber1]
AutomationProcessor: runAutomation: Could not execute automation:
automationAckSpontaneousAlarms
org.postgresql.util.PSQLException: A result was returned when none was
expected.
It does not execute the query, or at least does not give the expected results. My guess is it does a rollback on the transaction?
An ugly workaround is to use something like
create temp table foo123 on commit drop as select 1 from
functionname()
but that's really too ugly.
So it would be nice if you would allow statements with results in actions and just discard the results.
2010-07-09 13:08:46,185 WARN [VacuumdScheduler-2 Pool-fiber1]
AutomationProcessor: runAutomation: Could not execute automation:
automationAckSpontaneousAlarms
org.postgresql.util.PSQLException: A result was returned when none was
expected.
It does not execute the query, or at least does not give the expected results. My guess is it does a rollback on the transaction?
An ugly workaround is to use something like
create temp table foo123 on commit drop as select 1 from
functionname()
but that's really too ugly.
So it would be nice if you would allow statements with results in actions and just discard the results.