On 09-Feb-2021, at 14:16, raf wrote:
On Tue, Feb 09, 2021 at 12:19:21PM -0800, Bryn Llewellyn
wrote:
>
>
> On 09-Feb-2021, at 12:11, Tom Lane wrote:
>
> Bryn Llewellyn writes:
>> Here’s what I get when I do "otool -L /usr/local/bin/psql";
>
>> /usr/local/bin/psql:
>> /usr/local/lib/
On Tue, Feb 09, 2021 at 12:19:21PM -0800, Bryn Llewellyn
wrote:
>
>
> On 09-Feb-2021, at 12:11, Tom Lane wrote:
>
> Bryn Llewellyn writes:
> > Here’s what I get when I do "otool -L /usr/local/bin/psql";
>
> > /usr/local/bin/psql:
> > /usr/local/lib/libpq.5.dylib (compatibility version
On 09-Feb-2021, at 12:49, Adrian Klaver wrote:
On 2/9/21 12:19 PM, Bryn Llewellyn wrote:
> On 09-Feb-2021, at 12:11, Tom Lane wrote:
> Bryn Llewellyn writes:
>> Here’s what I get when I do "otool -L /usr/local/bin/psql";
>> /usr/local/bin/psql:
>> /usr/local/lib/libpq.5.dylib (compatibil
On 2/9/21 12:19 PM, Bryn Llewellyn wrote:
On 09-Feb-2021, at 12:11, Tom Lane wrote:
Bryn Llewellyn writes:
Here’s what I get when I do "otool -L /usr/local/bin/psql";
/usr/local/bin/psql:
/usr/local/lib/libpq.5.dylib (compatibility version 5.0.0, current
version 5.13.0)
On 09-Feb-2021, at 12:11, Tom Lane wrote:
Bryn Llewellyn writes:
> Here’s what I get when I do "otool -L /usr/local/bin/psql";
> /usr/local/bin/psql:
> /usr/local/lib/libpq.5.dylib (compatibility version 5.0.0, current
> version 5.13.0)
> /usr/local/opt/readline/lib/libreadline.
On 2/9/21 1:57 PM, Bryn Llewellyn wrote:
[snip]
In other words, different from what you see. I'm an ordinary end user. I don't even
think expllictly about “building" anything in the PostgreSQL system. I got into
this mess (as I believe) because I did this:
brew update
brew upgrade
A colleague
Bryn Llewellyn writes:
> Here’s what I get when I do "otool -L /usr/local/bin/psql";
> /usr/local/bin/psql:
> /usr/local/lib/libpq.5.dylib (compatibility version 5.0.0, current
> version 5.13.0)
> /usr/local/opt/readline/lib/libreadline.8.dylib (compatibility version
> 8.0.0, curren
On 09-Feb-2021, at 11:43, Tom Lane wrote:
Bryn Llewellyn writes:
> HAS ANYBODY ELSE SEEN WHAT I REPORT BELOW?
> First observation
> Now, when I copy a single line SQL command, terminated with semicolon and
> newline from the Text Edit app (with Command-C or the menu item) and then
> paste
Bryn Llewellyn writes:
> HAS ANYBODY ELSE SEEN WHAT I REPORT BELOW?
> First observation
> Now, when I copy a single line SQL command, terminated with semicolon and
> newline from the Text Edit app (with Command-C or the menu item) and then
> paste it into psql (with Command-V or the menu item)
paul.foers...@gmail.com wrote:
Hi Bryn,
> On 09. Feb, 2021, at 19:55, Bryn Llewellyn wrote:
>
> Using a MacBook Pro with the current Big Sur—Version 11.2 (20D64).
>
> I just upgraded to PostgreSQL 13.1. (Earlier, I was on 12.x.) Using psql, the
> behavior of ordinary copy-and-paste has change
Hi Bryn,
> On 09. Feb, 2021, at 19:55, Bryn Llewellyn wrote:
>
> Using a MacBook Pro with the current Big Sur—Version 11.2 (20D64).
>
> I just upgraded to PostgreSQL 13.1. (Earlier, I was on 12.x.) Using psql, the
> behavior of ordinary copy-and-paste has change dramatically, and for the
> wo
11 matches
Mail list logo
