From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: psql: \dl+ to list large objects privileges |
Date: | 2022-01-06 18:13:46 |
Message-ID: | 1154279.1641492826@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> writes:
>> I wonder if we shouldn't put these new tests in largeobject.sql instead.
>> (That would mean there are two expected-files to change, which is a bit
>> tedious, but it's not very hard.)
> I made the same changes to two files in the 'expected' directory:
> largeobject.out and largeobject_1.out.
> Although I must say that I still can't understand why more than one file
> with expected result is used for some tests.
Because the output sometimes varies across platforms. IIRC, the
case where largeobject_1.out is needed is for Windows, where the
file that gets inserted into one of the LOs might contain CR/LF
not just LF newlines, so the LO contents look different.
> Also, I decided to delete following line in the listLargeObjects
> function because all the other commands in describe.c do not contain it:
> myopt.topt.tuples_only = false;
Agreed, I'd done that already in my version of the patch.
> Second version (after splitting) is attached.
Pushed with some minor editorialization.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2022-01-06 18:21:32 | Re: Unifying VACUUM VERBOSE and log_autovacuum_min_duration output |
Previous Message | Paul A Jungwirth | 2022-01-06 18:08:54 | Re: SQL:2011 application time |