- 06 Jul, 2006 1 commit
-
-
Bruce Momjian authored
Studio 2005. Basically MS defined errcode in the headers with a typedef, so we have to #define it out of the way. While at it, fix a function declaration in plpython that didn't match the implementation (volatile missing). Magnus Hagander
-
- 26 Jun, 2006 1 commit
-
-
Bruce Momjian authored
-
- 24 Jun, 2006 1 commit
-
-
Tom Lane authored
-
- 07 Jun, 2006 1 commit
-
-
Bruce Momjian authored
o remove many WIN32_CLIENT_ONLY defines o add WIN32_ONLY_COMPILER define o add 3rd argument to open() for portability o add include/port/win32_msvc directory for system includes Magnus Hagander
-
- 28 May, 2006 1 commit
-
-
Tom Lane authored
and standard_conforming_strings; likewise for the other client programs that need it. As per previous discussion, a pg_dump dump now conforms to the standard_conforming_strings setting of the source database. We don't use E'' syntax in the dump, thereby improving portability of the SQL. I added a SET escape_strings_warning = off command to keep the dumps from getting a lot of back-chatter from that.
-
- 26 May, 2006 1 commit
-
-
Bruce Momjian authored
'off'. This allows pg_dump output with standard_conforming_strings = 'on' to generate proper strings that can be loaded into other databases without the backslash doubling we typically do. I have added the dumping of the standard_conforming_strings value to pg_dump. I also added standard backslash handling for plpgsql.
-
- 14 Apr, 2006 1 commit
-
-
Tom Lane authored
If a process abandons a wait in LockBufferForCleanup (in practice, only happens if someone cancels a VACUUM) just before someone else sends it a signal indicating the buffer is available, it was possible for the wakeup to remain in the process' semaphore, causing misbehavior next time the process waited for an lmgr lock. Rather than try to prevent the race condition directly, it seems best to make the lock manager robust against leftover wakeups, by having it repeat waiting on the semaphore if the lock has not actually been granted or denied yet.
-
- 05 Mar, 2006 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
Add DLLIMPORT for V1 headers, in case Win32 don't export all symbols.
-
- 03 Mar, 2006 1 commit
-
-
Bruce Momjian authored
have. This happens when MSVC uses pg_config.h generated by MinGW. Per report from Charles F. I. Savage
-
- 16 Feb, 2006 1 commit
-
-
Peter Eisentraut authored
64-bit platforms. by ITAGAKI Takahiro
-
- 03 Feb, 2006 1 commit
-
-
Bruce Momjian authored
MemSet on AIX by setting MEMSET_LOOP_LIMIT to zero. Add optimization to skip MemSet tests in MEMSET_LOOP_LIMIT == 0 case and just call memset() directly.
-
- 05 Jan, 2006 1 commit
-
-
Bruce Momjian authored
-
- 25 Dec, 2005 1 commit
-
-
Bruce Momjian authored
#define HIGHBIT (0x80) #define IS_HIGHBIT_SET(ch) ((unsigned char)(ch) & HIGHBIT) and removed CSIGNBIT and mapped it uses to HIGHBIT. I have also added uses for IS_HIGHBIT_SET where appropriate. This change is purely for code clarity.
-
- 06 Dec, 2005 1 commit
-
-
Tom Lane authored
on libintl which may or may not provide what we need. Make a few marginal cleanups to ensure this works. Andrew Dunstan and Tom Lane.
-
- 17 Nov, 2005 1 commit
-
-
Tom Lane authored
functionality, but I still need to make another pass looking at places that incidentally use arrays (such as ACL manipulation) to make sure they are null-safe. Contrib needs work too. I have not changed the behaviors that are still under discussion about array comparison and what to do with lower bounds.
-
- 15 Oct, 2005 1 commit
-
-
Bruce Momjian authored
-
- 21 Jul, 2005 1 commit
-
-
Bruce Momjian authored
-
- 18 Jul, 2005 1 commit
-
-
Tom Lane authored
checked that the pointer is actually word-aligned. Casting a non-aligned pointer to int32* is technically illegal per the C spec, and some recent versions of gcc actually generate bad code for the memset() when given such a pointer. Per report from Andrew Morrow.
-
- 02 Jul, 2005 1 commit
-
-
Bruce Momjian authored
Improve code clarity by using macros for E'' processing.
-
- 28 Jun, 2005 1 commit
-
-
Tom Lane authored
and pg_auth_members. There are still many loose ends to finish in this patch (no documentation, no regression tests, no pg_dump support for instance). But I'm going to commit it now anyway so that Alvaro can make some progress on shared dependencies. The catalog changes should be pretty much done.
-
- 08 Jun, 2005 1 commit
-
-
Tom Lane authored
transaction IDs, rather than like subtrans; in particular, the information now survives a database restart. Per previous discussion, this is essential for PITR log shipping and for 2PC.
-
- 25 May, 2005 1 commit
-
-
Bruce Momjian authored
them, the executation behavior could be unexpected.
-
- 11 May, 2005 1 commit
-
-
Neil Conway authored
memset() or MemSet() to a char *. For one, memset()'s first argument is a void *, and further void * can be implicitly coerced to/from any other pointer type.
-
- 28 Apr, 2005 1 commit
-
-
Tom Lane authored
to eliminate unnecessary deadlocks. This commit adds SELECT ... FOR SHARE paralleling SELECT ... FOR UPDATE. The implementation uses a new SLRU data structure (managed much like pg_subtrans) to represent multiple- transaction-ID sets. When more than one transaction is holding a shared lock on a particular row, we create a MultiXactId representing that set of transactions and store its ID in the row's XMAX. This scheme allows an effectively unlimited number of row locks, just as we did before, while not costing any extra overhead except when a shared lock actually has to be shared. Still TODO: use the regular lock manager to control the grant order when multiple backends are waiting for a row lock. Alvaro Herrera and Tom Lane.
-
- 29 Mar, 2005 1 commit
-
-
Tom Lane authored
change saves a great deal of space in pg_proc and its primary index, and it eliminates the former requirement that INDEX_MAX_KEYS and FUNC_MAX_ARGS have the same value. INDEX_MAX_KEYS is still embedded in the on-disk representation (because it affects index tuple header size), but FUNC_MAX_ARGS is not. I believe it would now be possible to increase FUNC_MAX_ARGS at little cost, but haven't experimented yet. There are still a lot of vestigial references to FUNC_MAX_ARGS, which I will clean up in a separate pass. However, getting rid of it altogether would require changing the FunctionCallInfoData struct, and I'm not sure I want to buy into that.
-
- 22 Feb, 2005 1 commit
-
-
Bruce Momjian authored
macros around strings that were missing them.
-
- 15 Feb, 2005 1 commit
-
-
Bruce Momjian authored
-
- 31 Dec, 2004 1 commit
-
-
PostgreSQL Daemon authored
Tag appropriate files for rc3 Also performed an initial run through of upgrading our Copyright date to extend to 2005 ... first run here was very simple ... change everything where: grep 1996-2004 && the word 'Copyright' ... scanned through the generated list with 'less' first, and after, to make sure that I only picked up the right entries ...
-
- 27 Sep, 2004 3 commits
-
-
Bruce Momjian authored
+ #if defined(_MSC_VER) || defined(__BORLANDC__) + #define WIN32_CLIENT_ONLY + #endif
-
Bruce Momjian authored
-
Neil Conway authored
Jurka.
-
- 26 Sep, 2004 1 commit
-
-
Tom Lane authored
-
- 23 Sep, 2004 1 commit
-
-
Bruce Momjian authored
Given that PostgreSQL will output a message complaining about it's absence if you're using SSL mode, I feel it's important that it gets a mention in the documentation at some point. Dominic Mitchell
-
- 16 Sep, 2004 1 commit
-
-
Tom Lane authored
as per recent discussions. Invent SubTransactionIds that are managed like CommandIds (ie, counter is reset at start of each top transaction), and use these instead of TransactionIds to keep track of subtransaction status in those modules that need it. This means that a subtransaction does not need an XID unless it actually inserts/modifies rows in the database. Accordingly, don't assign it an XID nor take a lock on the XID until it tries to do that. This saves a lot of overhead for subtransactions that are only used for error recovery (eg plpgsql exceptions). Also, arrange to release a subtransaction's XID lock as soon as the subtransaction exits, in both the commit and abort cases. This avoids holding many unique locks after a long series of subtransactions. The price is some additional overhead in XactLockTableWait, but that seems acceptable. Finally, restructure the state machine in xact.c to have a more orthogonal set of states for subtransactions.
-
- 10 Sep, 2004 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 09 Sep, 2004 1 commit
-
-
Bruce Momjian authored
-
- 29 Aug, 2004 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-