hcq/postgresql
1
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2026-04-13 10:07:02 +08:00
Code Issues Packages Projects Releases Wiki Activity

Commit Graph

  • 1783e5db3e Fix money type's send/receive functions to conform to recent widening of the datatype to int64. Per Andrew Chernow. Tom Lane 2007-08-21 03:14:36 +00:00
  • ffaaaf9918 Fix potential access-off-the-end-of-memory in varbit_out(): it fetched the byte after the last full byte of the bit array, regardless of whether that byte was part of the valid data or not. Found by buildfarm testing. Thanks to Stefan Kaltenbrunner for nailing down the cause. Tom Lane 2007-08-21 02:40:40 +00:00
  • 42110a6a6a Fix potential access-off-the-end-of-memory in varbit_out(): it fetched the byte after the last full byte of the bit array, regardless of whether that byte was part of the valid data or not. Found by buildfarm testing. Thanks to Stefan Kaltenbrunner for nailing down the cause. Tom Lane 2007-08-21 02:40:33 +00:00
  • c2e2ad7989 Fix potential access-off-the-end-of-memory in varbit_out(): it fetched the byte after the last full byte of the bit array, regardless of whether that byte was part of the valid data or not. Found by buildfarm testing. Thanks to Stefan Kaltenbrunner for nailing down the cause. Tom Lane 2007-08-21 02:40:26 +00:00
  • bbb7e05c32 Fix potential access-off-the-end-of-memory in varbit_out(): it fetched the byte after the last full byte of the bit array, regardless of whether that byte was part of the valid data or not. Found by buildfarm testing. Thanks to Stefan Kaltenbrunner for nailing down the cause. Tom Lane 2007-08-21 02:40:18 +00:00
  • c40f60db3f Fix potential access-off-the-end-of-memory in varbit_out(): it fetched the byte after the last full byte of the bit array, regardless of whether that byte was part of the valid data or not. Found by buildfarm testing. Thanks to Stefan Kaltenbrunner for nailing down the cause. Tom Lane 2007-08-21 02:40:12 +00:00
  • 1cee06ac02 Fix potential access-off-the-end-of-memory in varbit_out(): it fetched the byte after the last full byte of the bit array, regardless of whether that byte was part of the valid data or not. Found by buildfarm testing. Thanks to Stefan Kaltenbrunner for nailing down the cause. Tom Lane 2007-08-21 02:40:06 +00:00
  • 25a4a77985 Suppress uninitialized-variable warning. Tom Lane 2007-08-21 01:47:19 +00:00
  • 440a330a31 Fix a small 64-bit problem in tsearch patch. Tom Lane 2007-08-21 01:45:33 +00:00
  • 46dedde524 contrib/tsearch2 now fails its regression test because of conflicts with the core additions. For the moment I diked it out of contrib/Makefile. We should look at turning it into a backward-compatibility package. Tom Lane 2007-08-21 01:12:28 +00:00
  • 140d4ebcb4 Tsearch2 functionality migrates to core. The bulk of this work is by Oleg Bartunov and Teodor Sigaev, but I did a lot of editorializing, so anything that's broken is probably my fault. Tom Lane 2007-08-21 01:11:32 +00:00
  • 4e94d1f952 Add configure option --with-system-tzdata to use operating system time zone database. Peter Eisentraut 2007-08-20 08:53:12 +00:00
  • e1a1da9f4b minor typo fixes in CSVlog docs, per Michael Glaesemann Andrew Dunstan 2007-08-19 03:23:30 +00:00
  • de56b7cbdf Done: Bruce Momjian 2007-08-19 02:36:08 +00:00
  • fd801f4faa Provide for logfiles in machine readable CSV format. In consequence, rename redirect_stderr to logging_collector. Original patch from Arul Shaji, subsequently modified by Greg Smith, and then heavily modified by me. Andrew Dunstan 2007-08-19 01:41:25 +00:00
  • e53a548794 Add: Bruce Momjian 2007-08-16 19:02:15 +00:00
  • 817946bb04 Arrange to cache a ResultRelInfo in the executor's EState for relations that are not one of the query's defined result relations, but nonetheless have triggers fired against them while the query is active. This was formerly impossible but can now occur because of my recent patch to fix the firing order for RI triggers. Caching a ResultRelInfo avoids duplicating work by repeatedly opening and closing the same relation, and also allows EXPLAIN ANALYZE to "see" and report on these extra triggers. Use the same mechanism to cache open relations when firing deferred triggers at transaction shutdown; this replaces the former one-element-cache strategy used in that case, and should improve performance a bit when there are deferred triggers on a number of relations. Tom Lane 2007-08-15 21:39:50 +00:00
  • 5a3ec02312 Repair problems occurring when multiple RI updates have to be done to the same row within one query: we were firing check triggers before all the updates were done, leading to bogus failures. Fix by making the triggers queued by an RI update go at the end of the outer query's trigger event list, thereby effectively making the processing "breadth-first". This was indeed how it worked pre-8.0, so the bug does not occur in the 7.x branches. Per report from Pavel Stehule. Tom Lane 2007-08-15 19:16:12 +00:00
  • d8cb5391c2 Repair problems occurring when multiple RI updates have to be done to the same row within one query: we were firing check triggers before all the updates were done, leading to bogus failures. Fix by making the triggers queued by an RI update go at the end of the outer query's trigger event list, thereby effectively making the processing "breadth-first". This was indeed how it worked pre-8.0, so the bug does not occur in the 7.x branches. Per report from Pavel Stehule. Tom Lane 2007-08-15 19:16:04 +00:00
  • 37b57f1186 Repair problems occurring when multiple RI updates have to be done to the same row within one query: we were firing check triggers before all the updates were done, leading to bogus failures. Fix by making the triggers queued by an RI update go at the end of the outer query's trigger event list, thereby effectively making the processing "breadth-first". This was indeed how it worked pre-8.0, so the bug does not occur in the 7.x branches. Per report from Pavel Stehule. Tom Lane 2007-08-15 19:15:55 +00:00
  • 9cb8409762 Repair problems occurring when multiple RI updates have to be done to the same row within one query: we were firing check triggers before all the updates were done, leading to bogus failures. Fix by making the triggers queued by an RI update go at the end of the outer query's trigger event list, thereby effectively making the processing "breadth-first". This was indeed how it worked pre-8.0, so the bug does not occur in the 7.x branches. Per report from Pavel Stehule. Tom Lane 2007-08-15 19:15:47 +00:00
  • 5ff95e6b8e Add third idea about pulling data from indexes. Bruce Momjian 2007-08-15 15:53:30 +00:00
  • 811f91cf5a Fix whitespace in TODO. Bruce Momjian 2007-08-15 15:36:31 +00:00
  • 67f99d216a Fix oversight in async-commit patch: there were some places in heapam.c that still thought they could set HEAP_XMAX_COMMITTED immediately after seeing the other transaction commit. Make them use the same logic as tqual.c does to determine if the hint bit can be set yet. Tom Lane 2007-08-14 17:35:18 +00:00
  • 6ccc262d6d Done for ecpg: Bruce Momjian 2007-08-14 17:02:42 +00:00
  • 002b4781ba It seems we simply expected the same output for failure and success. Michael Meskes 2007-08-14 11:21:38 +00:00
  • 8187905913 It seems I always forget .in files. Michael Meskes 2007-08-14 10:56:20 +00:00
  • cbe74fafe5 Hopefully fixed missing CHAR_BIT symbol Michael Meskes 2007-08-14 10:54:57 +00:00
  • aa130f5c42 Fixed compiler warning for enum handling Michael Meskes 2007-08-14 10:32:47 +00:00
  • 146242fc9c As usual I forgot some files. :-) Michael Meskes 2007-08-14 10:19:14 +00:00
  • 635a0b9a86 - Finished major rewrite to use new protocol version - Really prepare statements - Added more regression tests - Added auto-prepare mode - Use '$n' for positional variables, '?' is still possible via ecpg option - Cleaned up the sources a little bit Michael Meskes 2007-08-14 10:01:54 +00:00
  • b83bd31bd9 TEMPORARILY make synchronous_commit default to OFF, so that we can get more thorough testing of async-commit mode from the buildfarm. This patch MUST get reverted before 8.3 release! Tom Lane 2007-08-13 19:27:12 +00:00
  • 647fd9a108 Fix two bugs induced in VACUUM FULL by async-commit patch. Tom Lane 2007-08-13 19:08:26 +00:00
  • a44af6df85 Document that the regexp split functions ignore zero-length matches in certain corner cases. Per discussion, the code does what we want, but it really needs to be documented that these functions act differently from regexp_matches. Tom Lane 2007-08-13 01:18:47 +00:00
  • b70d4a62ee Remove an "optimization" I installed in 2001, to make repalloc() attempt to enlarge the memory chunk in-place when it was feasible to do so. This turns out to not work well at all for scenarios involving repeated cycles of palloc/repalloc/pfree: the eventually freed chunks go into the wrong freelist for the next initial palloc request, and so we consume memory indefinitely. While that could be defended against, the number of cases where the optimization can still be applied drops significantly, and adjusting the initial sizes of StringInfo buffers makes it drop to almost nothing. Seems better to just remove the extra complexity. Per recent discussion and testing. Tom Lane 2007-08-12 20:39:14 +00:00
  • 70868c012f Increase the initial size of StringInfo buffers to 1024 bytes (from 256); likewise increase the initial size of the scanner's literal buffer to 1024 (from 128). Instrumentation of the regression tests suggests that this saves a useful amount of repalloc() traffic --- the number of calls occurring during one set of tests drops from about 6900 to about 3900. The old sizes were chosen in the late 90's with an eye to machines much smaller than are common today. Tom Lane 2007-08-12 20:18:06 +00:00
  • ae65ca312f Avoid memory leakage across successive calls of regexp_matches() or regexp_split_to_table() within a single query. This is only a partial solution, as it turns out that with enough matches per string these functions can also tickle a repalloc() misbehavior. But fixing that is a topic for a separate patch. Tom Lane 2007-08-11 19:16:41 +00:00
  • 1b70619311 Code review for regexp_matches/regexp_split patch. Refactor to avoid assuming that cached compiled patterns will still be there when the function is next called. Clean up looping logic, thereby fixing bug identified by Pavel Stehule. Share setup code between the two functions, add some comments, and avoid risky mixing of int and size_t variables. Clean up the documentation a tad, and accept all the flag characters mentioned in table 9-19 rather than just a subset. Tom Lane 2007-08-11 03:56:24 +00:00
  • 75cfea7f00 Fix uninitialized-memory bug in plpython proargnames patch. Per bug #3523 Tom Lane 2007-08-10 03:16:11 +00:00
  • d0e5c0c0ee Fix uninitialized-memory bug in plpython proargnames patch. Per bug #3523 Tom Lane 2007-08-10 03:16:04 +00:00
  • e32d51d541 Fix unintended change of output format for createlang/droplang -l. Missed these uses of printQuery() in FETCH_COUNT patch a year ago :-(. Per report from Tomoaki Sato. Tom Lane 2007-08-10 00:39:44 +00:00
  • 509bfd6a6b Fix unintended change of output format for createlang/droplang -l. Missed these uses of printQuery() in FETCH_COUNT patch a year ago :-(. Per report from Tomoaki Sato. Tom Lane 2007-08-10 00:39:31 +00:00
  • 3cb1617863 Fix search for SGML stylesheets to include the place where Gentoo keeps them. Brendan Jurd Tom Lane 2007-08-09 02:34:07 +00:00
  • faa1179678 Fix search for SGML stylesheets to include the place where Gentoo keeps them. Brendan Jurd Tom Lane 2007-08-09 02:33:58 +00:00
  • bbe3c02d38 Revise postmaster startup/shutdown logic to eliminate the problem that a constant flow of new connection requests could prevent the postmaster from completing a shutdown or crash restart. This is done by labeling child processes that are "dead ends", that is, we know that they were launched only to tell a client that it can't connect. These processes are managed separately so that they don't confuse us into thinking that we can't advance to the next stage of a shutdown or restart sequence, until the very end where we must wait for them to drain out so we can delete the shmem segment. Per discussion of a misbehavior reported by Keaton Adams. Tom Lane 2007-08-09 01:18:43 +00:00
  • c556b29a11 Fix a gradual memory leak in ExecReScanAgg(). Because the aggregation hash table is allocated in a child context of the agg node's memory context, MemoryContextReset() will reset but *not* delete the child context. Since ExecReScanAgg() proceeds to build a new hash table from scratch (in a new sub-context), this results in leaking the header for the previous memory context. Therefore, use MemoryContextResetAndDeleteChildren() instead. Neil Conway 2007-08-08 18:07:05 +00:00
  • 7dd8d4673f Fix a gradual memory leak in ExecReScanAgg(). Because the aggregation hash table is allocated in a child context of the agg node's memory context, MemoryContextReset() will reset but *not* delete the child context. Since ExecReScanAgg() proceeds to build a new hash table from scratch (in a new sub-context), this results in leaking the header for the previous memory context. Therefore, use MemoryContextResetAndDeleteChildren() instead. Neil Conway 2007-08-08 18:07:03 +00:00
  • 1de589bfcb Fix a gradual memory leak in ExecReScanAgg(). Because the aggregation hash table is allocated in a child context of the agg node's memory context, MemoryContextReset() will reset but *not* delete the child context. Since ExecReScanAgg() proceeds to build a new hash table from scratch (in a new sub-context), this results in leaking the header for the previous memory context. Therefore, use MemoryContextResetAndDeleteChildren() instead. Neil Conway 2007-08-08 18:07:02 +00:00
  • c5e86719b0 Fix a gradual memory leak in ExecReScanAgg(). Because the aggregation hash table is allocated in a child context of the agg node's memory context, MemoryContextReset() will reset but *not* delete the child context. Since ExecReScanAgg() proceeds to build a new hash table from scratch (in a new sub-context), this results in leaking the header for the previous memory context. Therefore, use MemoryContextResetAndDeleteChildren() instead. Neil Conway 2007-08-08 18:06:58 +00:00
  • 7824c695ac Fix a gradual memory leak in ExecReScanAgg(). Because the aggregation hash table is allocated in a child context of the agg node's memory context, MemoryContextReset() will reset but *not* delete the child context. Since ExecReScanAgg() proceeds to build a new hash table from scratch (in a new sub-context), this results in leaking the header for the previous memory context. Therefore, use MemoryContextResetAndDeleteChildren() instead. Neil Conway 2007-08-08 18:06:55 +00:00
  • af1022d2cd Fix thinko in multi-autovac-workers code: validity checks made by GUC assign hooks are supposed to be made whether doit is true or not. Tom Lane 2007-08-08 16:00:46 +00:00
  • 849ec99753 Adjust the output of MemoryContextStats() so that the stats for a child memory contexts is indented two spaces to the right of its parent context. This should make it easier to deduce the memory context hierarchy from the output of MemoryContextStats(). Neil Conway 2007-08-07 06:25:14 +00:00
  • 3605c8c877 Fix incorrect URI for cvs rsync Magnus Hagander 2007-08-06 07:58:06 +00:00
  • 99fa5f458c Fix pg_restore to guard against unexpected EOF while reading an archive file. Per report and partial patch from Chad Wagner. Tom Lane 2007-08-06 01:38:57 +00:00
  • b58230005b Fix pg_restore to guard against unexpected EOF while reading an archive file. Per report and partial patch from Chad Wagner. Tom Lane 2007-08-06 01:38:49 +00:00
  • fbf9179a27 Fix pg_restore to guard against unexpected EOF while reading an archive file. Per report and partial patch from Chad Wagner. Tom Lane 2007-08-06 01:38:40 +00:00
  • 6d1607dc3f Fix pg_restore to guard against unexpected EOF while reading an archive file. Per report and partial patch from Chad Wagner. Tom Lane 2007-08-06 01:38:32 +00:00
  • f614a2b508 Fix pg_restore to guard against unexpected EOF while reading an archive file. Per report and partial patch from Chad Wagner. Tom Lane 2007-08-06 01:38:24 +00:00
  • fcb9535e8a Fix pg_restore to guard against unexpected EOF while reading an archive file. Per report and partial patch from Chad Wagner. Tom Lane 2007-08-06 01:38:15 +00:00
  • df9ea6a1f1 Adjust configure so that it sets CFLAGS properly for Intel's icc even if the compiler is not defining __GNUC__. Per report from Dirk Tilger that it is possible for icc to not do that. Tom Lane 2007-08-05 15:43:00 +00:00
  • c8b7e811f3 Apparently icc doesn't always define __ICC, and it's more correct to check for __INTEL_COMPILER. Per report from Dirk Tilger. Not back-patched since I don't fully trust it yet ... Tom Lane 2007-08-05 15:11:40 +00:00
  • 8d30337566 Fix up bad layout of some comments (probably pg_indent's fault), and improve grammar a tad. Per Greg Stark. Tom Lane 2007-08-04 21:53:00 +00:00
  • 087a271327 Tweak for initdb: if more command-line arguments were specified than expected, exit with an error, rather than complaining about the error on stderr but continuing onward. Neil Conway 2007-08-04 21:01:09 +00:00
  • 4fd8d6b3e7 Fix crash caused by log_timezone patch if we attempt to emit any elog messages between the setting of log_line_prefix and the setting of log_timezone. We can't realistically set log_timezone any earlier than we do now, so the best behavior seems to be to use GMT zone if any timestamps are to be logged during early startup. Create a dummy zone variable with a minimal definition of GMT (in particular it will never know about leap seconds), so that we can set it up without reference to any external files. Tom Lane 2007-08-04 19:29:25 +00:00
  • 0b9d3d4dcd Fix a problem in my recent patch to initialize cancel_key for autovac workers as well as regular backends: if no regular backend launches before the autovac launcher tries to start an autovac worker, the postmaster would get an Assert fault due to calling PostmasterRandom before random_seed was initialized. Cleanest solution seems to be to take the initialization of random_seed out of ServerLoop and let PostmasterRandom do it for itself. Tom Lane 2007-08-04 03:15:49 +00:00
  • 2e24f4af49 Suppress time zone name (%Z) when logging timestamps in xlog.c startup on Windows. This is yet another manifestation of the problem that Windows returns time zone names that may be in a different encoding than we are using. I've put a better solution in HEAD, but the back branches need a simple patch. Per report from Hiroshi Saito. Tom Lane 2007-08-04 01:42:44 +00:00
  • f99e72fa51 Suppress time zone name (%Z) when logging timestamps in xlog.c startup on Windows. This is yet another manifestation of the problem that Windows returns time zone names that may be in a different encoding than we are using. I've put a better solution in HEAD, but the back branches need a simple patch. Per report from Hiroshi Saito. Tom Lane 2007-08-04 01:42:34 +00:00
  • fffafc5dca Suppress time zone name (%Z) when logging timestamps in xlog.c startup on Windows. This is yet another manifestation of the problem that Windows returns time zone names that may be in a different encoding than we are using. I've put a better solution in HEAD, but the back branches need a simple patch. Per report from Hiroshi Saito. Tom Lane 2007-08-04 01:42:24 +00:00
  • bdd6b62245 Switch over to using the src/timezone functions for formatting timestamps displayed in the postmaster log. This avoids Windows-specific problems with localized time zone names that are in the wrong encoding, and generally seems like a good idea to forestall other potential platform-dependent issues. To preserve the existing behavior that all backends will log in the same time zone, create a new GUC variable log_timezone that can only be changed on a system-wide basis, and reference log-related calculations to that zone instead of the TimeZone variable. Tom Lane 2007-08-04 01:26:54 +00:00
  • 73852bd520 Fix some sloppiness in the recent multiple-autovacuum-worker patch. It was not bothering to initialize is_autovacuum for regular backends, meaning there was a significant chance of the postmaster prematurely sending them SIGTERM during database shutdown. Also, leaving the cancel key unset for an autovac worker meant that any client could send it SIGINT, which doesn't sound especially good either. Tom Lane 2007-08-03 20:06:50 +00:00
  • 3f0245cb24 Update supported standalone VC++ version to 7.1+ only, and fix some bad data leftover in win32.mak. Magnus Hagander 2007-08-03 10:47:11 +00:00
  • 63872601e8 Move session_start out of MyProcPort stucture and make it a global called MyStartTime, so that we will be able to create a cookie for all processes for CSVlogs. It is set wherever MyProcPid is set. Take the opportunity to remove the now unnecessary session-only restriction on the %s and %c escapes in log_line_prefix. Andrew Dunstan 2007-08-02 23:39:45 +00:00
  • db97262ba5 Make sure syslogPipe runs in binary mode on Windows to avoid corrupting the pipe chunking protocol. Backport to 8.0 Andrew Dunstan 2007-08-02 23:20:22 +00:00
  • 6c77d7d73b Make sure syslogPipe runs in binary mode on Windows to avoid corrupting the pipe chunking protocol. Backport to 8.0 Andrew Dunstan 2007-08-02 23:18:47 +00:00
  • 1032186f0c Make sure syslogPipe runs in binary mode on Windows to avoid corrupting the pipe chunking protocol. Backport to 8.0 Andrew Dunstan 2007-08-02 23:17:20 +00:00
  • b34903453f Make sure syslogPipe runs in binary mode on Windows to avoid corrupting the pipe chunking protocol. Backport to 8.0 Andrew Dunstan 2007-08-02 23:15:27 +00:00
  • 3ca3c71141 Fix a memory leak in tuplestore_end(). Unlikely to be significant during normal operation, but tuplestore_end() ought to do what it claims to do. Neil Conway 2007-08-02 17:49:01 +00:00
  • 314a201ca6 Fix a memory leak in tuplestore_end(). Unlikely to be significant during normal operation, but tuplestore_end() ought to do what it claims to do. Neil Conway 2007-08-02 17:48:59 +00:00
  • cbf8f82824 Fix a memory leak in tuplestore_end(). Unlikely to be significant during normal operation, but tuplestore_end() ought to do what it claims to do. Neil Conway 2007-08-02 17:48:57 +00:00
  • 2bd26c5166 Fix a memory leak in tuplestore_end(). Unlikely to be significant during normal operation, but tuplestore_end() ought to do what it claims to do. Neil Conway 2007-08-02 17:48:54 +00:00
  • 494d6f809e Fix a memory leak in tuplestore_end(). Unlikely to be significant during normal operation, but tuplestore_end() ought to do what it claims to do. Neil Conway 2007-08-02 17:48:52 +00:00
  • c441e26ee8 Done: Bruce Momjian 2007-08-01 23:13:31 +00:00
  • 4a78cdeb6b Support an optional asynchronous commit mode, in which we don't flush WAL before reporting a transaction committed. Data consistency is still guaranteed (unlike setting fsync = off), but a crash may lose the effects of the last few transactions. Patch by Simon, some editorialization by Tom. Tom Lane 2007-08-01 22:45:09 +00:00
  • c722628a43 Fix strange quoting. Bruce Momjian 2007-08-01 22:24:32 +00:00
  • 4f49621aef Fix script quoting problem. Bruce Momjian 2007-08-01 22:23:01 +00:00
  • 3bc619342f Remove links to old Win32 source code ports. Bruce Momjian 2007-08-01 00:24:55 +00:00
  • c14066aa70 Fix a bug in the original implementation of redundant-join-clause removal: clauses in which one side or the other references both sides of the join cannot be removed as redundant, because that expression won't have been constrained below the join. Per report from Sergey Burladyan. Tom Lane 2007-07-31 19:54:27 +00:00
  • e938544bef Fix a bug in the original implementation of redundant-join-clause removal: clauses in which one side or the other references both sides of the join cannot be removed as redundant, because that expression won't have been constrained below the join. Per report from Sergey Burladyan. Tom Lane 2007-07-31 19:54:11 +00:00
  • 4e957954d6 Fix a bug in the original implementation of redundant-join-clause removal: clauses in which one side or the other references both sides of the join cannot be removed as redundant, because that expression won't have been constrained below the join. Per report from Sergey Burladyan. Tom Lane 2007-07-31 19:54:01 +00:00
  • 1be62b532b Fix a bug in the original implementation of redundant-join-clause removal: clauses in which one side or the other references both sides of the join cannot be removed as redundant, because that expression won't have been constrained below the join. Per report from Sergey Burladyan. Tom Lane 2007-07-31 19:53:50 +00:00
  • ed5d55dafe Fix a bug in the original implementation of redundant-join-clause removal: clauses in which one side or the other references both sides of the join cannot be removed as redundant, because that expression won't have been constrained below the join. Per report from Sergey Burladyan. Tom Lane 2007-07-31 19:53:37 +00:00
  • bc421c35b1 If we're gonna use ExecRelationIsTargetRelation here, might as well simplify a bit further. Tom Lane 2007-07-31 16:36:07 +00:00
  • fab6a867fd Fix security definer functions with polymorphic arguments. This case has never worked because fmgr_security_definer() neglected to pass the fn_expr information through. Per report from Viatcheslav Kalinin. Tom Lane 2007-07-31 15:50:17 +00:00
  • 59bb0282d4 Fix security definer functions with polymorphic arguments. This case has never worked because fmgr_security_definer() neglected to pass the fn_expr information through. Per report from Viatcheslav Kalinin. Tom Lane 2007-07-31 15:50:07 +00:00
  • bfe4f48146 Fix security definer functions with polymorphic arguments. This case has never worked because fmgr_security_definer() neglected to pass the fn_expr information through. Per report from Viatcheslav Kalinin. Tom Lane 2007-07-31 15:50:01 +00:00
  • 5bd7b83426 Fix security definer functions with polymorphic arguments. This case has never worked because fmgr_security_definer() neglected to pass the fn_expr information through. Per report from Viatcheslav Kalinin. Tom Lane 2007-07-31 15:49:54 +00:00
  • 310578efee Fix security definer functions with polymorphic arguments. This case has never worked because fmgr_security_definer() neglected to pass the fn_expr information through. Per report from Viatcheslav Kalinin. Tom Lane 2007-07-31 15:49:49 +00:00
  • dffad02856 Slight refactor for ExecOpenScanRelation(): we can use ExecRelationIsTargetRelation() to check if the relation is a target rel, rather than scanning through the result relation array ourselves. Neil Conway 2007-07-27 19:09:04 +00:00
  • dc6dc0f63a Update conformance information about bigint type Peter Eisentraut 2007-07-27 10:37:52 +00:00
  • e4f4a7f5a4 Remove FileUnlink(), which wasn't being used anywhere and interacted poorly with the recent patch to log temp file sizes at removal time. Doesn't seem worth fixing since it's unused. In passing, make a few elog messages conform to the message style guide. Tom Lane 2007-07-26 15:15:18 +00:00