| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ResourceOwner refactoring |
| Date: | 2022-11-01 12:43:09 |
| Message-ID: | CA+TgmoYEVaq8-F9x71AL00bkAkYVawmb625HYciFfm-GtF4Tzw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 1, 2022 at 6:39 AM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> However, I feel that trying to enforce a particular order moves the
> goalposts. If we need that, let's add it as a separate patch later.
I don't really see it that way, because with the current
implementation, we do all resources of a particular type together,
before moving on to the next type. That seems like a valuable property
to preserve, and I think we should.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-11-01 12:54:35 | Re: pg_upgrade allows itself to be run twice |
| Previous Message | Daniel Verite | 2022-11-01 12:43:03 | Re: [patch] \g with multiple result sets and \watch with copy queries |