Logs are below. This happens on master, and on 10. I suspect it is an
issue with something regarding ecpg. Wondering what I am doing wrong.
== creating temporary instance==
== initializing database system ==
==
Logs are below. This happens on master, and on 10. I suspect it is an
issue with something regarding ecpg. Wondering what I am doing wrong.
== creating temporary instance==
== initializing database system ==
==
Hi folks 👋
Forgive me if I'm getting the mailing list etiquette wrong — first time poster.
I ended up sitting next to Thomas Munro at PGDU 2018 and talking about testing.
While trying to get `make check` running on my macbook, I think I may have
fixed this issue.
System Integrity Protection st
Samuel Cochran writes:
> System Integrity Protection strips dynamic linker (dyld) environment
> variables, such as DYLD_LIBRARY_PATH, during exec(2) [1]
Yeah. I wish Apple would just fix that silliness ... I'll spare you the
rant about why it's stupid, but it is. (BTW, last I looked, it's not
On Fri, Dec 7, 2018, at 5:26 PM, Tom Lane wrote:
> Interesting proposal, but I think it needs work.
Absolutely! I only hacked it together to the point that it worked on my laptop
and illustrated the approach. :-)
> * As coded, this only fixes the problem for references to libpq, not
> any of our
Chris Travers writes:
> Logs are below. This happens on master, and on 10. I suspect it is an
> issue with something regarding ecpg. Wondering what I am doing wrong.
"make check" generally won't work on OSX unless you've disabled SIP:
https://www.howtogeek.com/230424/how-to-disable-system-int
On Tue, Sep 18, 2018 at 2:14 AM Tom Lane wrote:
> Chris Travers writes:
> > Logs are below. This happens on master, and on 10. I suspect it is an
> > issue with something regarding ecpg. Wondering what I am doing wrong.
>
> "make check" generally won't work on OSX unless you've disabled SIP:
>
Thomas Munro writes:
> On Tue, Sep 18, 2018 at 2:14 AM Tom Lane wrote:
>> "make check" generally won't work on OSX unless you've disabled SIP:
>> https://www.howtogeek.com/230424/how-to-disable-system-integrity-protection-on-a-mac-and-why-you-shouldnt/
> Aha! It looks like it was important to r
Hi folks 👋
Forgive me if I'm getting the mailing list etiquette wrong — first time poster.
I ended up sitting next to Thomas Munro at PGDU 2018 and talking about testing.
While trying to get `make check` running on my macbook, I think I may have
fixed this issue.
System Integrity Protection st
Samuel Cochran writes:
> System Integrity Protection strips dynamic linker (dyld) environment
> variables, such as DYLD_LIBRARY_PATH, during exec(2) [1]
Yeah. I wish Apple would just fix that silliness ... I'll spare you the
rant about why it's stupid, but it is. (BTW, last I looked, it's not
On Fri, Dec 7, 2018, at 5:26 PM, Tom Lane wrote:
> Interesting proposal, but I think it needs work.
Absolutely! I only hacked it together to the point that it worked on my laptop
and illustrated the approach. :-)
> * As coded, this only fixes the problem for references to libpq, not
> any of our
Chris Travers writes:
> Logs are below. This happens on master, and on 10. I suspect it is an
> issue with something regarding ecpg. Wondering what I am doing wrong.
"make check" generally won't work on OSX unless you've disabled SIP:
https://www.howtogeek.com/230424/how-to-disable-system-int
On Tue, Sep 18, 2018 at 2:14 AM Tom Lane wrote:
> Chris Travers writes:
> > Logs are below. This happens on master, and on 10. I suspect it is an
> > issue with something regarding ecpg. Wondering what I am doing wrong.
>
> "make check" generally won't work on OSX unless you've disabled SIP:
>
Thomas Munro writes:
> On Tue, Sep 18, 2018 at 2:14 AM Tom Lane wrote:
>> "make check" generally won't work on OSX unless you've disabled SIP:
>> https://www.howtogeek.com/230424/how-to-disable-system-integrity-protection-on-a-mac-and-why-you-shouldnt/
> Aha! It looks like it was important to r
14 matches
Mail list logo
