| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
|
|
|
|
| |
owned by postgres, doing "pg_ctl start" as root could allow a privilege
escalation attack, as pointed out by iDEFENSE. Of course the postmaster would
fail, but we ought to fail a little sooner to protect sysadmins unfamiliar
with Postgres. The chosen fix is to disable root use of pg_ctl in all cases,
just to be confident there are no other holes.
|
|
|
|
|
|
|
|
| |
is called. getByte presents a can't happen situation as no function
can return a TINYINT because pg doesn't have an equivalent type.
Make this throw an exception if we get to this point.
Thanks to Christian Niles.
|
|
|
|
|
|
| |
http://archives.postgresql.org/pgsql-hackers/2004-10/msg00464.php.
I plan a more permanent fix in HEAD, but for the back branches it seems
best to just touch the places that actually have a problem.
|
| |
|
| |
|
|
|
|
|
|
| |
This seems the cleanest way of fixing its lack of a shutdown callback,
which was preventing it from working correctly in a query that didn't
run it to completion. Per bug report from Szima GÄbor.
|
| |
|
|
|
|
|
| |
it really hadn't, due to double output of previous command's response.
Fix prevents recursive entry to libpq routines. Found by Jan Wieck.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
was large enough to be batched and the tuples fell into a batch where
there were no inner tuples at all. Thanks to Xiaoyu Wang for finding a
test case that exposed this long-standing bug.
|
| |
|
|
|
|
|
|
|
|
| |
function to prevent multiple threads using automatic cursors on
the same connection from stomping over each others cursor.
Originally Jan Wieck, re-reported by Jack Orenstein after
accidental removal.
|
|
|
|
|
|
|
|
|
|
| |
assuming it had been set instead of correctly calling the
isUpdateable() method which sets the flag if needed. This usually
worked because moveToCurrentRow is only useful after a
moveToInsertRow call which would set the flag, but this is not
required.
David Bucciarelli
|
|
|
|
|
| |
Not sure why this isn't causing serious problems in some simple tests,
but it definitely isn't going to do anything desirable...
|
|
|
|
|
| |
branch. I wasn't excited about doing this when the first report came in,
but now that we have two of 'em, I suppose it had better get fixed.
|
| |
|
|
|
|
|
| |
made in passing for 8.0, but now that we have a bug report showing it's
needed, we should put it into 7.4 branch.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
value of 'start' could be past the end of the page, if the page was
split by some concurrent inserting process since we visited it. In
this situation the code could look at bogus entries and possibly find
a match (since after all those entries still contain what they had
before the split). This would lead to 'specified item offset is too large'
followed by 'PANIC: failed to add item to the page', as reported by Joe
Conway for scenarios involving heavy concurrent insertion activity.
|
| |
|
|
|
|
| |
Andrew Dunstan.
|
| |
|
| |
|
| |
|
|
|
|
| |
that refers to a now-deleted userid. Per gripe from Chris Ochs.
|
|
|
|
| |
From Donald Fraser.
|
|
|
|
|
| |
because both Java's String constructor and pg's input parser strip
off backslashes.
|
|
|
|
|
|
| |
for transaction commits that occurred just before the checkpoint. This is
an EXTREMELY serious bug --- kudos to Satoshi Okada for creating a
reproducible test case to prove its existence.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
that contain rights granted by non-owners. Per bug report from
Nishad Prakash.
|
|
|
|
|
|
| |
force relcache rebuild for the other table as well as the column's
own table. Otherwise, already-cached foreign key triggers will stop
working. Per example from Alexander Pravking.
|
|
|
|
|
|
| |
the retrieved data to zero, which doesn't work for non-integer values.
Oliver Dauben
|
|
|
|
|
|
|
| |
This is required by SQL spec to avoid failures in cases like
SELECT sum(win)/sum(lose) FROM ... GROUP BY ... HAVING sum(lose) > 0;
AFAICT we have gotten this wrong since day one. Kudos to Holger Jakobs
for being the first to notice.
|
| |
|
| |
|
| |
|
|
|
|
| |
et al.
|
| |
|
| |
|
|
|
|
|
| |
- Variables that are out of scope, were not removed all the time.
- Make a varchar NULL set everything to 0 when not using indicators.
|
|
|
|
| |
Markus Schaber
|
|
|
|
|
|
| |
protocol, or encountering other connection failures.
Laurent Sylvain
|
|
|
|
|
| |
after the end of results. You could still call a number of methods
on them like getXXX, updateXXX, and updateRow().
|