Re: proposal: psql –help reflecting service or URI usage

2021-03-08 Thread Paul Förster
cked it and made my changes there. Then I did a diff to the original and posted it here. I don't even know if this is the correct workflow. I saw gitgub being mentioned a couple of times but I don't have an account, nor do I even know how it works. I was pretty surprised to see the

Re: proposal: psql –help reflecting service or URI usage

2021-03-06 Thread Paul Förster
Hi Euler, > On 01. Mar, 2021, at 15:42, Euler Taveira wrote: > > We try to limit it to 80 characters but it is not a hard limit. Long > descriptions should certainly be split into multiple lines. got that, thanks. > The question is: how popular is service and connection URIs? well, we use th

Re: proposal: psql –help reflecting service or URI usage

2021-03-06 Thread Paul Förster
Hi Mark, sorry for the delay. > On 01. Mar, 2021, at 17:02, Mark Dilger wrote: > > The output from --help should fit in a terminal window with only 80 > characters width. For example, in src/bin/scripts/createuser.c the line > about --interactive is wrapped: I see. > You can find counter-e

Re: proposal: psql –help reflecting service or URI usage

2021-03-01 Thread Paul Förster
Hi Mark, I revisited my first admittedly naive and faulty attempt. > On 28. Feb, 2021, at 19:10, Paul Förster wrote: > >> but of course being careful to still fit in the line length limit. > I agree to all, thanks. What is the line length limit? still, what is the line length

Re: proposal: psql –help reflecting service or URI usage

2021-02-28 Thread Paul Förster
Hi Mark, > On 28. Feb, 2021, at 17:54, Mark Dilger wrote: > > "definited" is a typo. yes, definitely a typo, sorry. Thanks for pointing this out. > Should this say "as defined in pg_service.conf"? That's the default, but the > user might have $PGSERVICEFILE set to something else. Perhaps yo

proposal: psql –help reflecting service or URI usage

2021-02-28 Thread Paul Förster
Hi, I'd like to propose a patch to psql --help output: Currently it is: Usage: psql [OPTION]... [DBNAME [USERNAME]] ... Connection options: -h, --host=HOSTNAME database server host or socket directory (default: "local socket") -p, --port=PORT database server port (default:

Re: configure and DocBook XML

2020-11-27 Thread Paul Förster
Hi Tom, > On 27. Nov, 2020, at 18:54, Tom Lane wrote: > > See the other thread I pointed to. ok, thanks. Cheers, Paul

Re: configure and DocBook XML

2020-11-27 Thread Paul Förster
Hi Tom, > On 27. Nov, 2020, at 16:29, Tom Lane wrote: > > To me, it makes sense to have an option to do that, but I do find it > surprising that it's the default. ok, last question: is there an option for configure to not check for DocBook? It's not installed and PostgreSQL doesn't need it to

Re: configure and DocBook XML

2020-11-27 Thread Paul Förster
Hi Tom, > On 26. Nov, 2020, at 17:48, Tom Lane wrote: > > If you don't have the docbook stylesheets, but you do have xmllint, > configure's probe will cause xmllint to try to download those > stylesheets off the net. For me, that always succeeds, but it > takes two or three seconds. I find it

Re: configure and DocBook XML

2020-11-26 Thread Paul Förster
Hi Tom, > On 26. Nov, 2020, at 17:21, Tom Lane wrote: > > On machines where I don't have the stylesheets installed, it always > takes several seconds (2 or 3, I think, though I've not put a stopwatch > on it). 15 to 20 sec does seem like a lot, so it makes me wonder if > Paul's network environm

Re: configure and DocBook XML

2020-11-26 Thread Paul Förster
Hi Alvaro, > On 26. Nov, 2020, at 15:19, Alvaro Herrera wrote: > > One way to know for sure would be to run it under strace, and see where > it takes a large number of seconds. Maybe something like > strace -f -etrace=%network -T -tt -o/tmp/configure.trace ./configure ok, I'll try this. Thank

Re: configure and DocBook XML

2020-11-26 Thread Paul Förster
Hi Alvaro, > On 26. Nov, 2020, at 14:47, Alvaro Herrera wrote: > > My guess is that it's related to trying to obtain stylesheets from > remote Internet locations that are missing locally. I don't know DocBook at all, so I can't say. But it takes about the same time, whether I run configure on

configure and DocBook XML

2020-11-26 Thread Paul Förster
Hi, I always compile PostgreSQL from source and never install a pre-compiled package. When I run configure, the last check, which is for DocBook XML always takes very long compared to all others. It's about 15 to 20 secs or so. I noticed that with many configure scripts, not only the one of Pos

Re: Building 12.3 from source on Mac

2020-07-23 Thread Paul Förster
Hi Tom, > On 23. Jul, 2020, at 16:50, Tom Lane wrote: > > You should see what "file" reports these as, but there's a good > bet that these are 32-bit code and won't even run on Catalina. yes, they seem pretty old: paul@meerkat:/usr/local/lib$ file libintl.* libintl.3.4.3.dylib: Mach-

Re: Building 12.3 from source on Mac

2020-07-23 Thread Paul Förster
Hi Tom, > On 23. Jul, 2020, at 16:03, Tom Lane wrote: > > Looks like what you lack is a symlink libintl.dylib -> libintl.3.4.3.dylib > in /usr/local/lib. It's not real clear to me why you'd have .a and .la > files and no versionless symlink, because all of those files would > just be used for l

Re: Building 12.3 from source on Mac

2020-07-23 Thread Paul Förster
Hi Tom, > On 23. Jul, 2020, at 15:42, Tom Lane wrote: > > Kind of looks like you *did* install gettext as Daniel suggested > (macOS proper would never put anything under /usr/local). Maybe > you did not ask for that specifically, but installed some package > that requires it? > > However, Appl

Re: Building 12.3 from source on Mac

2020-07-23 Thread Paul Förster
Hi Daniel, > On 23. Jul, 2020, at 12:37, Daniel Gustafsson wrote: > gettext is not shipped by default with macOS, you will have to install it > separately via your favourite package manager or by building from source. To > verify you can always search your system for the required header file: >

Building 12.3 from source on Mac

2020-07-23 Thread Paul Förster
Hi, I'm not sure this is the right list, but I have a problem concerning building PostgreSQL 12.3 from source on a Mac. I do: ./configure \ --prefix=${pgTargetDir} \ --enable-nls \ --with-perl \ --with-python \ --with-libxml \ --with-tclconfig=/usr/lib64 \ PG_SYSROOT