Re: Separate connection handling from backends

Поиск
Список
Период
Сортировка
От Adam Brusselback
Тема Re: Separate connection handling from backends
Дата
Msg-id CAMjNa7dCdgJX4Asj0L+JddL0+Zgqm04DB6JHvjBpw2ALqT25Mg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Separate connection handling from backends  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Ответы Re: Separate connection handling from backends  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers
Дерево обсуждения
BTW, it just occurred to me that having this separation would make it relatively easy to support re-directing DML queries from a replica to the master; if the backend throws the error indicating you tried to write data, the connection layer could re-route that.

This also sounds like it would potentially allow re-routing the other way where you know the replica contains up-to-date data, couldn't you potentially re-direct read only queries to your replicas?

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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: WIP: Faster Expression Processing and Tuple Deforming (including JIT)
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Compiler warnings