| From: | Tim Clarke <tim(dot)clarke(at)minerva(dot)info> |
|---|---|
| To: | Glen Huang <heyhgl(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to implement expiration in PostgreSQL? |
| Date: | 2021-04-01 14:31:53 |
| Message-ID: | b0133d49-685b-d2c7-8dfb-8427f1ab1c88@minerva.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 01/04/2021 15:23, Glen Huang wrote:
> I wish one cron job could rule them all, but since a person can decide to join at any time, her expiration (e.g., after 1 hour) can also happen at any time. So one cron job won’t cut it if a member’s expiration has to bee accurate.
One cron job running every 5 minutes should do?
Tim Clarke MBCS
IT Director
Direct: +44 (0)1376 504510 | Mobile: +44 (0)7887 563420
Telephone: Witham: +44(0)1376 503500 | London: +44 (0)20 3009 0853 | Frankfurt: +49 (0)69 7191 6000 | Hong Kong: +852 5803 1687 | Toronto: +1 647 503 2848
Web: https://www.manifest.co.uk/
Minerva Analytics Ltd - A Solactive Company
9 Freebournes Court | Newland Street | Witham | Essex | CM8 2BL | United Kingdom
________________________________
Copyright: This e-mail may contain confidential or legally privileged information. If you are not the named addressee you must not use or disclose such information, instead please report it to admin(at)minerva(dot)info<mailto:admin(at)minerva(dot)info>
Legal: Minerva Analytics is the trading name of: Minerva Analytics Ltd: Registered in England Number 11260966 & The Manifest Voting Agency Ltd: Registered in England Number 2920820 Registered Office at above address. Please Click Here https://www.manifest.co.uk/legal/ for further information.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glen Huang | 2021-04-01 14:36:56 | Re: How to implement expiration in PostgreSQL? |
| Previous Message | Glen Huang | 2021-04-01 14:23:42 | Re: How to implement expiration in PostgreSQL? |