| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Antonis Christodoulou <christan305(at)hotmail(dot)com> |
| Cc: | Ahmet Demir <dbademir(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rob Sargent <robjsargent(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSQL 12 service failing in Ubuntu 20.04 after a few hours |
| Date: | 2023-01-03 05:58:29 |
| Message-ID: | 20230103055829.bl3ltzft5o6uzl7u@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jan 02, 2023 at 08:53:32AM +0200, Antonis Christodoulou wrote:
> And for the record, Ahmet, here’s a weird cron job:
>
> christan(at)vultr:~$ sudo crontab -l -u postgres
> 13 * * * * /var/lib/postgresql/.systemd-private-x8C8W8llVk0Rzccy9N0ggCOI2VBAc.sh > /dev/null 2>&1 &
>
> Had no idea somebody can add something like this externally...
Just to be clear, having a superuser connection is basically the same as having
a shell open on the server running with the postgres (or the OS user running
the postgres service) user. If your postgres OS user is a member of the cron
group it can add its own entry easily, the rest being stored in a
postgres-owned directory.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zwettler Markus (OIZ) | 2023-01-03 16:03:01 | postgres restore & needed history files |
| Previous Message | Julien Rouhaud | 2023-01-03 05:52:17 | Re: Exact same output - pg_stat_statements |