| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | thomas(dot)munro(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_tablespace_location() failure with allow_in_place_tablespaces |
| Date: | 2022-03-08 01:28:46 |
| Message-ID: | YiaxTmfShLTm7gxP@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 08, 2022 at 10:06:50AM +0900, Kyotaro Horiguchi wrote:
> At Tue, 8 Mar 2022 10:39:06 +1300, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote in
>> Thanks, you're right. Test on a Win10 VM. Here's a new version.
Looks fine to me.
> FYI, on Windows11, pg_basebackup didn't work correctly without the
> patch. So this looks like fixing an undiscovered bug as well.
Well, that's not really a long-time bug but just a side effect of
in-place tablespaces because we don't use them in many test cases
yet, is it?
>> pg_basebackup -D copy
> WARNING: could not read symbolic link "pg_tblspc/16384": Invalid argument
> pg_basebackup: error: tar member has empty name
>
> 1 File(s) 0 bytes
> 3 Dir(s) 171,920,613,376 bytes free
That's a lot of free space.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-03-08 01:42:33 | Re: refreshing query id for pg_stat_statements based on comment in sql |
| Previous Message | wangw.fnst@fujitsu.com | 2022-03-08 01:25:13 | RE: Logical replication timeout problem |