| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Igor Korot <ikorot01(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Fwd: Log file |
| Date: | 2018-10-31 07:00:21 |
| Message-ID: | 233be564bfa8cba4084e8d1a031880b777b43d37.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-odbc |
Igor Korot wrote:
> Now is there a command to flush the log - delete the content of it?
No, managing the logs is outside of PostgreSQL's responsibility.
But it shouldn't be a problem to do this outside the database.
Of course you could write a funtion in PostgreSQL that uses one
of the "untrusted" procedural languages to do it for you.
> All I'm looking for in the log are DDL commands - CREATE/ALTER/DELETE ones.
You mean DROP, right?
You can set "log_statement = 'ddl'" for that.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicolas Paris | 2018-10-31 08:00:00 | Re: Full-text Search - Thesaurus relationships |
| Previous Message | Laurenz Albe | 2018-10-31 06:56:28 | Re: Full-text Search - Thesaurus relationships |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Takahashi, Ryohei | 2018-10-31 07:53:02 | SQLExecDirectW returns SQL_SUCCESS even if sql finishes with error |
| Previous Message | Igor Korot | 2018-10-31 04:32:33 | Re: Fwd: Log file |