| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> As you can see, psql reconnect as any user if the password is same as
> foo. Of course this is due to the careless password setting, but I
> think it's better to prompt ANY TIME the user tries to switch to
> another user. Comments?
Yeah, I agree. Looks like a simple change in dbconnect():
/*
* Use old password if no new one given (if you didn't have an old
* one, fine)
*/
if (!pwparam && oldconn)
pwparam = PQpass(oldconn);
to
/*
* Use old password (if any) if no new one given and we are
* reconnecting as same user
*/
if (!pwparam && oldconn && PQuser(oldconn) && userparam &&
strcmp(PQuser(oldconn), userparam) == 0)
pwparam = PQpass(oldconn);
regards, tom lane
|
| |
|
|
|
|
| |
Tatsuo.
|
| |
|
|
|
|
|
| |
regarding timezone_hour, timezone_minute vs. tz_hour, tz_minute.
Document the former.
|
|
|
|
|
|
|
|
|
| |
current_timestamp, current_date for ODBC compatibility.
Add more functions to odbc.sql catalog extension, use new CREATE OR
REPLACE FUNCTION.
Document iODBC/unixODBC build options.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
That patch broke the ability to read data from binary cursors.
--Barry Lind
Modified Files:
pgsql/src/interfaces/jdbc/org/postgresql/Connection.java
pgsql/src/interfaces/jdbc/org/postgresql/ResultSet.java
pgsql/src/interfaces/jdbc/org/postgresql/core/QueryExecutor.java
pgsql/src/interfaces/jdbc/org/postgresql/jdbc1/Connection.java
pgsql/src/interfaces/jdbc/org/postgresql/jdbc1/ResultSet.java
pgsql/src/interfaces/jdbc/org/postgresql/jdbc2/Connection.java
pgsql/src/interfaces/jdbc/org/postgresql/jdbc2/ResultSet.java
pgsql/src/interfaces/jdbc/org/postgresql/jdbc2/UpdateableResultSet.java
|
|
|
|
|
| |
output (from pdfjadetex). Also updated instructions to install documentation
processing toolchain.
|
|
|
|
|
|
|
| |
NOTICE added about error location (same method already used by plpgsql
executor). Add checking of pg_proc row xmin/cmin to ensure that
plpgsql functions will be recompiled after they've been modified by
CREATE OR REPLACE FUNCTION.
|
| |
|
| |
|
|
|
|
|
|
|
| |
rather than having its own somewhat half-baked notion of what a type
declaration looks like. This is necessary now to ensure that plpgsql
will think a 'timestamp' variable has the same semantics as 'timestamp'
does in the main SQL grammar; and it should avoid divergences in future.
|
|
|
|
|
|
| |
for nested typecasts. It now produces a column header of 'timestamptz'
for 'SELECT CURRENT_TIMESTAMP', rather than 'text' as it was doing for
awhile there.
|
|
|
|
|
| |
transforming CASE expressions. This was definitely confusing
FigureColname, and might lead to bad things elsewhere as well.
|
|
|
|
|
| |
copy of code that knows about displaying types with typmod info.
Needed so that it does the right thing with timestamp datatypes now.
|
|
|
|
| |
refer to the renamed column. Brent Verner, with a little help from tgl.
|
|
|
|
| |
agree with CURRENT_TIME(n).
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
lookup info in the relcache for index access method support functions.
This makes a huge difference for dynamically loaded support functions,
and should save a few cycles even for built-in ones. Also tweak dfmgr.c
so that load_external_function is called only once, not twice, when
doing fmgr_info for a dynamically loaded function. All per performance
gripe from Teodor Sigaev, 5-Oct-01.
|
|
|
|
|
|
|
| |
\d table display in psql, I noticed that tableinfo.triggers
is not used once it is set.
Greg Sabino Mullane
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
and modified from Simplified Chinese translations for backend,
pgsql, pg_dump and libpq. I've appended their names to zh_TW.po.
forth
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on words as opposed to lines, which means that all of the
following work in psql:
\d foo \d bar
\d foo; \d bar
\d foo \d bar;;
\d foo; <space>
This one also uses "true and false" and strips semicolons
for the following backslash commands: \C \c \d \e \i \o \s \z
Greg Sabino Mullane
|
| |
|
|
|
|
|
|
|
|
|
| |
readability. Bizarre '(long *) TRUE' return convention is gone,
in favor of just raising an error internally in dynahash.c when
we detect hashtable corruption. HashTableWalk is gone, in favor
of using hash_seq_search directly, since it had no hope of working
with non-LONGALIGNable datatypes. Simplify some other code that was
made undesirably grotty by promixity to HashTableWalk.
|
|
|
|
| |
Oliver Elphick
|
|
|
|
|
|
| |
> > thus I ask you to apply the following patch, to make it work.
Zeugswetter Andreas SB SD
|
| |
|
|
|
|
|
| |
per Jan Varga <varga@utcru.sk>
Fix up spacing and formatting.
|
|
|
|
| |
Use CAST() mechanism to define CURRENT_TIME and CURRENT_TIMESTAMP.
|
|
|
|
|
| |
COMMENT ON LARGE OBJECT command instead, but no time for it now.)
Fix some code that would not work with OIDs > 2G.
|
|
|
|
| |
text output.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
type coercion after failing to find an exact match in pg_proc, but before
considering interpretations that involve a function call with one or
more argument type coercions. This avoids surprises wherein what looks
like a type coercion is interpreted as coercing to some third type and
then to the destination type, as in Dave Blasby's bug report of 3-Oct-01.
See subsequent discussion in pghackers.
|
|
|
|
|
| |
index opclasses; they might be default for some other datatype,
in which case we mustn't suppress 'em.
|
|
|
|
| |
From Teodor Sigaev.
|
|
|
|
| |
but timestamp now wants it to mean something.
|
| |
|