| Age | Commit message (Collapse) | Author |
|---|
|
|
|
modify the previous \password patch to use it instead of depending
on a not-officially-exported function. Per discussion.
|
|
password encryption. Also alter createuser command to the same effect.
|
|
|
|
|
|
Backpatch to 8.0.X.
|
|
other stuff; change \du and \dg to be role-aware (Stefan Kaltenbrunner).
Also make tab completion fetch the list of GUC variables from pg_settings
instead of having a hard-wired copy of the list (Tom Lane).
|
|
Adrian Maier
|
|
|
|
|
|
|
|
100.000,0.
Eugen Nedelcu
|
|
mode to only affect the presentation of normal query results, not the
output of psql slash commands. Documentation updated. I also made
some unrelated minor psql cleanup. Per suggestion from Stuart Cooper.
|
|
if you have previously issued a \cd command.
Greg Sabino Mullane
|
|
psql. i.e. "\pset format troff-ms". The patch also corrects some
problems with the "latex" format, notably defining an extra column in
the output table, and correcting some alignment issues; it also
changes the output to match the border setting as documented in the
manual page and as shown with the "aligned" format.
The troff-ms output is mostly identical to the latex output allowing
for the differences between the two typesetters.
The output should be saved in a file and piped as follows:
cat file | tbl | troff -T ps -ms > file.ps
or
tbl file | troff -T ps -ms > file.ps
Because it contains tabs, you'll need to redirect psql output or use
"script", rather than pasting from a terminal window, due to the tabs
which can be replaced with spaces.
Roger Leigh
|
|
|
|
Add support for snprintf '+', 'h', and %* length settings.
|
|
implementation doesn't export out via libpq and get used by a user
application.
|
|
macros around strings that were missing them.
|
|
|
|
after an unknown or failed psql backslash command, and also while
discarding "extra" arguments of a putatively valid backslash command.
In the case of an unknown/failed command, make sure we discard the
whole rest of the line, rather than trying to resume at the next
backslash. Per discussion with Thomer Gil.
|
|
This prevents the next psql prompt from showing up on the end of the
last history line.
|
|
|
|
|
|
|
|
|
|
|
|
default on Win32.
|
|
|
|
password.
Make password error message a #define and use it consistently.
Sean Chittenden
|
|
for getpid().
|
|
|
|
|
|
|
|
|
|
patches.
|
|
|
|
Dennis Bjorklund
|
|
environment variables.
|
|
control-z requirement.
|
|
|
|
There are various things left to do: contrib dbsize and oid2name modules
need work, and so does the documentation. Also someone should think about
COMMENT ON TABLESPACE and maybe RENAME TABLESPACE. Also initlocation is
dead, it just doesn't know it yet.
Gavin Sherry and Tom Lane.
|
|
conversion of basic ASCII letters. Remove all uses of strcasecmp and
strncasecmp in favor of new functions pg_strcasecmp and pg_strncasecmp;
remove most but not all direct uses of toupper and tolower in favor of
pg_toupper and pg_tolower. These functions use the same notions of
case folding already developed for identifier case conversion. I left
the straight locale-based folding in place for situations where we are
just manipulating user data and not trying to match it to built-in
strings --- for example, the SQL upper() function is still locale
dependent. Perhaps this will prove not to be what's wanted, but at
the moment we can initdb and pass regression tests in Turkish locale.
|
|
/* This scrolls off the screen when using /dev/tty */
|
|
errors in internally-generated queries, such as those submitted by
plpgsql functions. Per recent discussions with Fabien Coelho.
|
|
recent discussion. The lexer is used for both SQL command text and
backslash commands. The purpose of this change is to make it easier to
track the behavior of the backend's SQL lexer --- essentially identical
flex rules are now used by psql. Also, this cleans up a lot of very
squirrelly code in mainloop.c and command.c. The flex code is somewhat
bulkier than the removed code, but should be lots easier to maintain.
|
|
cases involving writes. Per recent discussion about the possibility
of close-time failures on some filesystems. There is a TODO item for
this, too.
|
|
pg_malloc, to avoid linker failures on same platforms.
|
|
little more sane. Some parts of the code was using a static function
xmalloc() that did safe memory allocation (where "safe" means "bail
out on OOM"), but most of it was just invoking calloc() or malloc()
directly. Now almost everything invokes xmalloc() or xcalloc().
|
|
Zach Irmen
|
