Sponsored Content
Full Discussion: PostgreSQL vacuum in cron
Special Forums UNIX and Linux Applications PostgreSQL vacuum in cron Post 302563439 by rbatte1 on Tuesday 11th of October 2011 08:22:24 AM
Old 10-11-2011
If there is unhandled output, then it will be e-mailed to the user running the cron job. This will be a unix mail, so probably it will stay on the server running the request rather than route off to a Windows based mail service.

If you have handled the output by putting it in a file somewhere, then you need to read it and interpret any messages. What does your code look like?





Robin
Liverpool/Blackburn
UK
 
END(7)							  PostgreSQL 9.2.7 Documentation						    END(7)

NAME
END - commit the current transaction SYNOPSIS
END [ WORK | TRANSACTION ] DESCRIPTION
END commits the current transaction. All changes made by the transaction become visible to others and are guaranteed to be durable if a crash occurs. This command is a PostgreSQL extension that is equivalent to COMMIT(7). PARAMETERS
WORK, TRANSACTION Optional key words. They have no effect. NOTES
Use ROLLBACK(7) to abort a transaction. Issuing END when not inside a transaction does no harm, but it will provoke a warning message. EXAMPLES
To commit the current transaction and make all changes permanent: END; COMPATIBILITY
END is a PostgreSQL extension that provides functionality equivalent to COMMIT(7), which is specified in the SQL standard. SEE ALSO
BEGIN(7), COMMIT(7), ROLLBACK(7) PostgreSQL 9.2.7 2014-02-17 END(7)
All times are GMT -4. The time now is 09:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy