From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | MauMau <maumau307(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [patch] pg_copy - a command for reliable WAL archiving |
Date: | 2014-08-20 14:08:25 |
Message-ID: | CAM-w4HNQNE7+G4gR=4BbwqarBk2aKgVAXyR-RV+cwD1Hq+mTjg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Aug 20, 2014 at 2:27 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Hmm, the real trick here is linkat(... "/proc/self/foobar"), not the
> O_TMPFILE: you can have an open file descriptor to an "invisible" file
> simply by creating a normal file and unlinking it. I looked at linkat()
> yesterday but the idea of using /proc/self didn't occur to me. Nasty
> trick :-( It seems linkat() is quite a bit more portable than
> O_TMPFILE, fortunately ...
Supposedly linkat(2) on Linux refuses to create a link to a file that
was opened normally and had its last link removed with unlink(2) due
to concerns that this would create security holes.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-08-20 14:14:09 | Re: [patch] pg_copy - a command for reliable WAL archiving |
Previous Message | Alvaro Herrera | 2014-08-20 13:50:56 | Re: [patch] pg_copy - a command for reliable WAL archiving |