Re: ResourceOwner refactoring - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ResourceOwner refactoring
Date
Msg-id CA+TgmoYEVaq8-F9x71AL00bkAkYVawmb625HYciFfm-GtF4Tzw@mail.gmail.com
Whole thread Raw
In response to Re: ResourceOwner refactoring  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On Tue, Nov 1, 2022 at 6:39 AM Heikki Linnakangas <hlinnaka@iki.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



pgsql-hackers by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: [patch] \g with multiple result sets and \watch with copy queries
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_upgrade allows itself to be run twice