How to guard PostgreSQL from overcharged and/or malicious (read-only) queries?

Поиск
Список
Период
Сортировка
От Stefan Keller
Тема How to guard PostgreSQL from overcharged and/or malicious (read-only) queries?
Дата
Msg-id AANLkTi=B7aRvBDCOZONYgSPVVVb6OuTTOe8QmOejKc-O@mail.gmail.com
обсуждение исходный текст
Ответы Re: How to guard PostgreSQL from overcharged and/or malicious (read-only) queries?  (Alban Hertroys <dalroi@solfertje.student.utwente.nl>)
Список pgsql-general
I'd like to guard postgres from overcharged and/or malicious queries.

The queries are strinctly read-only (from a SQL users perspective).
For doing this I'd like to code two functions (preferrably pl/pgsql):

1. Filter out all SQL commands which are *not* read-only (no
DROP/DELETE/UPDATE/TRUNCATE).
2. Get the estimated time (units) from PostgreSQL planner in a
reliable way (if possible standard/ANSI).

Can someone give me some hints?

Yours, S.

В списке pgsql-general по дате отправления:

Предыдущее
От: Oleg Bartunov
Дата:
Сообщение: Re: FTS phrase searches
Следующее
От: AI Rumman
Дата:
Сообщение: pg_statsinfo problem