Re: The use of (mb)print.c from psql in the scripts directory

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: The use of (mb)print.c from psql in the scripts directory
Date: 2005-10-25 20:52:37
Message-ID: 200510252052.j9PKqbk18830@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Martijn van Oosterhout wrote:
-- Start of PGP signed section.
> Currently createlang and droplang use these two files mbprint.c and
> print.c to access the function printQuery() just to handle the
> displaying of the current languages. Is there any particular reason why
> it can't be made to use the version in libpq?
>
> In particular, does anyone really rely on the possibility of createlang
> invoking your pager to display the list of languages? It really does,
> you just have to make your terminal really small to see it.
>
> The reason I'm asking is because I'm working on the interaction between
> psql and the pager and keep running into issues w.r.t. createlang using
> the same code.

Yea, I think it would be good to use libpq rather than grab from psql.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2005-10-25 21:15:40 Re: expanded \df+ display broken in beta4
Previous Message Yohanes Santoso 2005-10-25 20:37:34 Re: determining random_page_cost value