My point is simply this: The lack of a clear formal process for feature
requests leads to this degradation in the conversation. Without a formalized
structure, the conversation devolves rapidly into an argument over semantics
and word choice. It is not my contention that the "core" developers ne
a person if they met them. Perhaps we should go fishing for
some help from one of those "University Places"? From people outside the
Computer Science department? Maybe even some people in Industrial
Psychology? Somebody probably needs a Master's project
--
Sean Utt
* Actually I&
And then what? Make the search box on www.postgresql.org able to handle an
email address as search text without throwing a shoe?
Search for [EMAIL PROTECTED] or any other 'email' address from the postgres
home page. Barfage every time.
Easy for some isn't easy for all, apparently. Left that out
- Original Message -
From: "Bruce Momjian" <[EMAIL PROTECTED]>
-- snip --
I would like to clean up our documentation to consistently use these
words. Objections?
(Who says were obsessive?) :-)
-- more snip --
Did you mean, "Who says we're obsessive?" ;-)
Sean
---
ginal Message -
From: "Andrew Dunstan" <[EMAIL PROTECTED]>
To: "Sean Utt" <[EMAIL PROTECTED]>
Cc:
Sent: Sunday, October 30, 2005 3:05 PM
Subject: Re: [HACKERS] pg_dump option to dump only functions
You have omitted the "case 0" line following the comme
In what might be called my spare time, I was looking at pg_dump.c to see
about adding an option to dump only functions, and I think a comment got
pushed out of place in the section for handling arguments:
395 case 'X':
396 if (strcmp
It won't work properly that way. SIGINT gets sent to all the members
of the process group, not just the child. Psql isn't responsible for
sending ctrl-c through to the child.
Except that if I am in less, and I do CONTROL-C, it doesn't do anything at
all.
It doesn't exit.
If I send a kill
I failed to mention that I also tend to type CONTROL-C when I forget that
putty acts like an xterm, and doesn't need CONTROL-C to copy text into the
clipboard. In that case, aborting the pager, and leaving the terminal
trashed requiring me to exit psql, stty sane, and start up psql again is
really
If you send a recent version of vim a CONTROL-C, and you're just sitting
there at a prompt, it gives you a hint:
Type :quit to exit Vim
Any reason not to just trap the CONTROL-C in psql when paging and offer a
hint? Especially since we don't really know that the user really wanted to
type CONT
I was wonderring, because I create a lot of server side utility functions,
whether adding an option to pg_dump to just dump functions has been
considered. I did a quick perusal of the code, and noted that there is a
separate section within pg_dump to get the functions, but it is not able to
be trig
10 matches
Mail list logo
