On Fri, Oct 21, 2016 at 8:29 AM, Peter Eisentraut
wrote:
> On 8/16/16 1:05 PM, Tom Lane wrote:
>> Oh, interesting. It had occurred to me that we might be able to dodge
>> this issue if we started to recommend using unnamed POSIX semaphores
>> instead of SysV. (Obviously we'd want to check perfor
On 8/16/16 1:05 PM, Tom Lane wrote:
> Oh, interesting. It had occurred to me that we might be able to dodge
> this issue if we started to recommend using unnamed POSIX semaphores
> instead of SysV. (Obviously we'd want to check performance, but it's
> at least a plausible alternative.) I had not
Peter Eisentraut writes:
> A brief look through the code and some reading between the lines of the
> documentation shows that it only cleans up shared memory segments that
> are no longer attached to, but there is no such check for semaphores.
Oh, interesting. It had occurred to me that we might
On 8/16/16 11:24 AM, Tom Lane wrote:
> Not sure I believe that --- the cases that have been reported to us
> involved postgres processes that were still alive but had had their
> SysV semaphore sets deleted out from under them. Likely the SysV
> shmem segments too, but that wouldn't cause any obse
On Tue, Aug 16, 2016 at 5:24 PM, Tom Lane wrote:
> Magnus Hagander writes:
> > On Aug 16, 2016 5:11 PM, "Tom Lane" wrote:
> >> Dunno, it was still working the last time I used Fedora for anything
> much.
> >> Admittedly, that was about three years ago. But the issue would still
> >> arise if y
Magnus Hagander writes:
> On Aug 16, 2016 5:11 PM, "Tom Lane" wrote:
>> Dunno, it was still working the last time I used Fedora for anything much.
>> Admittedly, that was about three years ago. But the issue would still
>> arise if you prefer "pg_ctl start".
> There are two independent changes
On Aug 16, 2016 5:11 PM, "Tom Lane" wrote:
>
> Magnus Hagander writes:
> > On Aug 16, 2016 4:43 PM, "Tom Lane" wrote:
> >> Rather, the problem arises when J. Ordinary User does
> >> nohup postmaster &
> >> and then logs out.
>
> > I think this is a partially different issue though. They already
Magnus Hagander writes:
> On Aug 16, 2016 4:43 PM, "Tom Lane" wrote:
>> Rather, the problem arises when J. Ordinary User does
>> nohup postmaster &
>> and then logs out.
> I think this is a partially different issue though. They already broke the
> nohup approach earlier with a different change,
On Aug 16, 2016 4:43 PM, "Tom Lane" wrote:
>
> Peter Eisentraut writes:
> > On 8/16/16 8:53 AM, Greg Stark wrote:
> >> That's a system level change though. How would a normal user manage
this?
>
> > Arguably, if you are a normal user, you probably shouldn't be using
> > systemd to start system se
Peter Eisentraut writes:
> On 8/16/16 8:53 AM, Greg Stark wrote:
>> That's a system level change though. How would a normal user manage this?
> Arguably, if you are a normal user, you probably shouldn't be using
> systemd to start system services under your own account.
I'm not totally sure, but
On 8/16/16 8:53 AM, Greg Stark wrote:
> That's a system level change though. How would a normal user manage this?
Arguably, if you are a normal user, you probably shouldn't be using
systemd to start system services under your own account.
--
Peter Eisentraut http://www.2ndQuadrant.c
On Tue, Aug 16, 2016 at 12:41 AM, Josh Berkus wrote:
> Presumably people just need to add the system account tag to the unit
> file, no?
That's a system level change though. How would a normal user manage this?
--
greg
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
On 16 August 2016 at 08:33, Tom Lane wrote:
> Josh Berkus writes:
> > On 08/15/2016 05:18 PM, Tom Lane wrote:
> >> Well, yeah, it's easy to fix once you know you need to do so. The
> >> complaint is basically that out-of-the-box, it's broken, and it's
> >> not very clear what was gained by brea
Josh Berkus writes:
> On 08/15/2016 05:18 PM, Tom Lane wrote:
>> Well, yeah, it's easy to fix once you know you need to do so. The
>> complaint is basically that out-of-the-box, it's broken, and it's
>> not very clear what was gained by breaking it.
> You're welcome to argue with Lennart about t
On 08/15/2016 05:18 PM, Tom Lane wrote:
> Josh Berkus writes:
>> On 08/15/2016 02:43 PM, Tom Lane wrote:
>>> Last I heard, there's an exclusion for "system" accounts, so an
>>> installation that's using the Fedora-provided pgsql account isn't
>>> going to have a problem. It's homebrew installs ru
Josh Berkus writes:
> On 08/15/2016 02:43 PM, Tom Lane wrote:
>> Last I heard, there's an exclusion for "system" accounts, so an
>> installation that's using the Fedora-provided pgsql account isn't
>> going to have a problem. It's homebrew installs running under
>> ordinary-user accounts that are
On 08/15/2016 02:43 PM, Tom Lane wrote:
> Josh Berkus writes:
>> On 07/10/2016 10:56 AM, Joshua D. Drake wrote:
>>> tl;dr; Systemd 212 defaults to remove all IPC (including SYSV memory)
>>> when a user "fully" logs out.
>
>> That looks like it was under discussion in April, though. Do we have
>>
Josh Berkus writes:
> On 07/10/2016 10:56 AM, Joshua D. Drake wrote:
>> tl;dr; Systemd 212 defaults to remove all IPC (including SYSV memory)
>> when a user "fully" logs out.
> That looks like it was under discussion in April, though. Do we have
> confirmation it was never fixed? I'm not seeing
On 07/10/2016 10:56 AM, Joshua D. Drake wrote:
> Hackers,
>
> This just came across my twitter feed:
>
> https://lists.freedesktop.org/archives/systemd-devel/2014-April/018373.html
>
> tl;dr; Systemd 212 defaults to remove all IPC (including SYSV memory)
> when a user "fully" logs out.
That loo
On 11 July 2016 at 17:49, Bernd Helmle wrote:
>
>
> --On 11. Juli 2016 13:25:51 +0800 Craig Ringer
> wrote:
>
> > Perhaps by uid threshold in login.defs?
>
> systemd's configure.ac has this:
>
> AC_ARG_WITH(system-uid-max,
> AS_HELP_STRING([--with-system-uid-max=UID]
> [M
--On 11. Juli 2016 13:25:51 +0800 Craig Ringer
wrote:
> Perhaps by uid threshold in login.defs?
systemd's configure.ac has this:
AC_ARG_WITH(system-uid-max,
AS_HELP_STRING([--with-system-uid-max=UID]
[Maximum UID for system users]),
[SYSTEM_UID_MAX="$withval"],
On 11 July 2016 at 01:56, Joshua D. Drake wrote:
> Hackers,
>
> This just came across my twitter feed:
>
> https://lists.freedesktop.org/archives/systemd-devel/2014-April/018373.html
>
> tl;dr; Systemd 212 defaults to remove all IPC (including SYSV memory) when
> a user "fully" logs out.
>
>
The
On 10/07/2016 19:56, Joshua D. Drake wrote:
> Hackers,
>
> This just came across my twitter feed:
>
> https://lists.freedesktop.org/archives/systemd-devel/2014-April/018373.html
>
> tl;dr; Systemd 212 defaults to remove all IPC (including SYSV memory)
> when a user "fully" logs out.
>
AFAIK it
Hackers,
This just came across my twitter feed:
https://lists.freedesktop.org/archives/systemd-devel/2014-April/018373.html
tl;dr; Systemd 212 defaults to remove all IPC (including SYSV memory)
when a user "fully" logs out.
JD
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
24 matches
Mail list logo
