> On 18 Aug 2023, at 02:47, Michael Paquier wrote:
>
> On Thu, Aug 17, 2023 at 06:09:31PM +1000, Peter Smith wrote:
>> Ping.
>
> Funnily enough, I was looking at this entry yesterday, before you
> replied, and was wondering what's happening here.
It was a combination of summer vacation, doing C
On Fri, Aug 18, 2023 at 10:47 AM Michael Paquier wrote:
>
> On Thu, Aug 17, 2023 at 06:09:31PM +1000, Peter Smith wrote:
> > Ping.
>
> Funnily enough, I was looking at this entry yesterday, before you
> replied, and was wondering what's happening here.
>
> > I thought v2 was ready to be pushed, bu
On Thu, Aug 17, 2023 at 06:09:31PM +1000, Peter Smith wrote:
> Ping.
Funnily enough, I was looking at this entry yesterday, before you
replied, and was wondering what's happening here.
> I thought v2 was ready to be pushed, but then this thread went silent
> for 3 months
Change looks fine, so ap
On Thu, May 11, 2023 at 7:09 PM Peter Smith wrote:
>
> On Thu, May 11, 2023 at 6:30 PM Daniel Gustafsson wrote:
> >
> > > On 11 May 2023, at 07:41, Peter Smith wrote:
> >
> > > While reviewing another patch for the file info.c, I noticed some
> > > misplaced colon (':') in the verbose logs for p
On Thu, May 11, 2023 at 6:30 PM Daniel Gustafsson wrote:
>
> > On 11 May 2023, at 07:41, Peter Smith wrote:
>
> > While reviewing another patch for the file info.c, I noticed some
> > misplaced colon (':') in the verbose logs for print_rel_infos().
>
> That spelling was introduced in c2e9b2f28818
> On 11 May 2023, at 07:41, Peter Smith wrote:
> While reviewing another patch for the file info.c, I noticed some
> misplaced colon (':') in the verbose logs for print_rel_infos().
That spelling was introduced in c2e9b2f28818 which was the initial import of
pg_upgrade into contrib/ for the 9.0
