Re: [HACKERS] [PATCH] Pattern based listeners for asynchronousmessaging (LISTEN/NOTIFY)
| От | Markus Sintonen |
|---|---|
| Тема | Re: [HACKERS] [PATCH] Pattern based listeners for asynchronousmessaging (LISTEN/NOTIFY) |
| Дата | |
| Msg-id | CAMpj9JZzZ83Te81mL3+HY-U2rwMp3AQQjZ4M9=H2SOsETuthxg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] [PATCH] Pattern based listeners for asynchronousmessaging (LISTEN/NOTIFY) (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
| Список | pgsql-hackers |
The following does not work:
LISTEN 'foo%'
Neither this:
LISTEN SIMILAR TO "foo%"
This works:
LISTEN "foo%"
But it does not act as a pattern.
We could change the SIMILAR TO something like following (accepting also type of the pattern), for example:
LISTEN PATTERN 'foo%' TYPE 'similar'
LISTEN PATTERN 'foo*' TYPE 'ltree'
Or
LISTEN PATTERN 'foo%' USING 'similar'
Or
LISTEN MATCH 'foo%' USING 'similar'
Or
LISTEN MATCH 'foo%' TYPE 'similar'
Documentation is coming up.
2017-07-31 23:30 GMT+03:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
On 7/31/17 16:13, Markus Sintonen wrote:
> This patch has no know backward compatibility issues with the existing
> /LISTEN///UNLISTEN/ features. This is because patch extends the existing
> syntax by accepting quoted strings which define the patterns as opposed
> to the existing SQL literals.
I don't see that in the patch. Your patch changes the syntax LISTEN
ColId to mean a regular expression.
Even then, having LISTEN "foo" and LISTEN 'foo' mean different things
would probably be confusing.
I would think about specifying an operator somewhere in the syntax, like
you have with LISTEN SIMILAR TO. It would even be nice if a
non-built-in operator could be used for matching names.
Documentation is missing in the patch.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: