1. 19 Feb, 2001 1 commit
  2. 04 Jan, 2001 1 commit
  3. 01 Dec, 2000 1 commit
  4. 16 Nov, 2000 1 commit
  5. 26 Oct, 2000 1 commit
  6. 28 Jun, 2000 1 commit
    • Tom Lane's avatar
      First phase of memory management rewrite (see backend/utils/mmgr/README · 1aebc361
      Tom Lane authored
      for details).  It doesn't really do that much yet, since there are no
      short-term memory contexts in the executor, but the infrastructure is
      in place and long-term contexts are handled reasonably.  A few long-
      standing bugs have been fixed, such as 'VACUUM; anything' in a single
      query string crashing.  Also, out-of-memory is now considered a
      recoverable ERROR, not FATAL.
      Eliminate a large amount of crufty, now-dead code in and around
      memory management.
      Fix problem with holding off SIGTRAP, SIGSEGV, etc in postmaster and
      backend startup.
      1aebc361
  7. 30 May, 2000 1 commit
  8. 04 Apr, 2000 1 commit
    • Tom Lane's avatar
      Fix bug noted by Bruce: FETCH in an already-aborted transaction block · 708f82f1
      Tom Lane authored
      would crash, due to premature invocation of SetQuerySnapshot().  Clean
      up problems with handling of multiple queries by splitting
      pg_parse_and_plan into two routines.  The old code would not, for
      example, do the right thing with END; SELECT... submitted in one query
      string when it had been in transaction abort state, because it'd decide
      to skip planning the SELECT before it had executed the END.  New
      arrangement is simpler and doesn't force caller to plan if only
      parse+rewrite is needed.
      708f82f1
  9. 16 Dec, 1999 1 commit
  10. 10 Dec, 1999 1 commit
  11. 22 Nov, 1999 1 commit
  12. 07 Nov, 1999 1 commit
  13. 15 Jul, 1999 1 commit
  14. 25 May, 1999 2 commits
  15. 13 May, 1999 1 commit
    • Tom Lane's avatar
      Rip out QueryTreeList structure, root and branch. Querytree · 507a0a2a
      Tom Lane authored
      lists are now plain old garden-variety Lists, allocated with palloc,
      rather than specialized expansible-array data allocated with malloc.
      This substantially simplifies their handling and eliminates several
      sources of memory leakage.
      Several basic types of erroneous queries (syntax error, attempt to
      insert a duplicate key into a unique index) now demonstrably leak
      zero bytes per query.
      507a0a2a
  16. 30 Mar, 1999 1 commit
  17. 09 Mar, 1999 1 commit
    • Marc G. Fournier's avatar
      · f34240de
      Marc G. Fournier authored
      Changes to fix/improve the dynamic loading on NT
      
      From: Horak Daniel <horak@mmp.plzen-city.cz>
      f34240de
  18. 13 Feb, 1999 1 commit
  19. 08 Feb, 1999 1 commit
  20. 27 Jan, 1999 2 commits
  21. 24 Jan, 1999 1 commit
    • Tom Lane's avatar
      Replace typtoout() and gettypelem() with a single routine, · d03e9873
      Tom Lane authored
      so that fetching an attribute value needs only one SearchSysCacheTuple call
      instead of two redundant searches.  This speeds up a large SELECT by about
      ten percent, and probably will help GROUP BY and SELECT DISTINCT too.
      d03e9873
  22. 14 Dec, 1998 1 commit
    • Marc G. Fournier's avatar
      · 7c3b7d27
      Marc G. Fournier authored
      Initial attempt to clean up the code...
      
      Switch sprintf() to snprintf()
      Remove any/all #if 0 -or- #ifdef NOT_USED -or- #ifdef FALSE sections of
      	code
      7c3b7d27
  23. 27 Nov, 1998 1 commit
  24. 01 Sep, 1998 2 commits
  25. 24 Aug, 1998 1 commit
    • Bruce Momjian's avatar
      This is the final state of the rule system for 6.4 after the · 15cb32d9
      Bruce Momjian authored
          patch is applied:
      
      	Rewrite rules on relation level work fine now.
      
      	Event qualifications on insert/update/delete  rules  work
      	fine now.
      
      	I  added  the  new  keyword  OLD to reference the CURRENT
      	tuple. CURRENT will be removed in 6.5.
      
      	Update rules can  reference  NEW  and  OLD  in  the  rule
      	qualification and the actions.
      
      	Insert/update/delete rules on views can be established to
      	let them behave like real tables.
      
      	For  insert/update/delete  rules  multiple  actions   are
      	supported  now.   The  actions  can also be surrounded by
      	parantheses to make psql  happy.   Multiple  actions  are
      	required if update to a view requires updates to multiple
      	tables.
      
      	Regular users  are  permitted  to  create/drop  rules  on
      	tables     they     have     RULE     permissions     for
      	(DefineQueryRewrite() is  now  able  to  get  around  the
      	access  restrictions  on  pg_rewrite).  This enables view
      	creation for regular users too. This  required  an  extra
      	boolean  parameter  to  pg_parse_and_plan() that tells to
      	set skipAcl on all rangetable entries  of  the  resulting
      	queries.       There      is      a      new     function
      	pg_exec_query_acl_override()  that  could  be   used   by
      	backend utilities to use this facility.
      
      	All rule actions (not only views) inherit the permissions
      	of the event relations  owner.  Sample:  User  A  creates
      	tables    T1    and    T2,   creates   rules   that   log
      	INSERT/UPDATE/DELETE on T1 in T2 (like in the  regression
      	tests  for rules I created) and grants ALL but RULE on T1
      	to user B.  User B  can  now  fully  access  T1  and  the
      	logging  happens  in  T2.  But user B cannot access T2 at
      	all, only the rule actions can. And due to  missing  RULE
      	permissions on T1, user B cannot disable logging.
      
      	Rules  on  the  attribute  level are disabled (they don't
      	work properly and since regular users are  now  permitted
      	to create rules I decided to disable them).
      
      	Rules  on  select  must have exactly one action that is a
      	select (so select rules must be a view definition).
      
      	UPDATE NEW/OLD rules  are  disabled  (still  broken,  but
      	triggers can do it).
      
      	There are two new system views (pg_rule and pg_view) that
      	show the definition of the rules or views so the db admin
      	can  see  what  the  users do. They use two new functions
      	pg_get_ruledef() and pg_get_viewdef() that are  builtins.
      
      	The functions pg_get_ruledef() and pg_get_viewdef() could
      	be used to implement rule and view support in pg_dump.
      
      	PostgreSQL is now the only database system I  know,  that
      	has rewrite rules on the query level. All others (where I
      	found a  rule  statement  at  all)  use  stored  database
      	procedures  or  the  like  (triggers as we call them) for
      	active rules (as some call them).
      
          Future of the rule system:
      
      	The now disabled parts  of  the  rule  system  (attribute
      	level,  multiple  actions on select and update new stuff)
      	require a complete new rewrite handler from scratch.  The
      	old one is too badly wired up.
      
      	After  6.4  I'll  start to work on a new rewrite handler,
      	that fully supports the attribute level  rules,  multiple
      	actions on select and update new.  This will be available
      	for 6.5 so we get full rewrite rule capabilities.
      
      Jan
      15cb32d9
  26. 19 Aug, 1998 1 commit
    • Bruce Momjian's avatar
      heap_fetch requires buffer pointer, must be released; heap_getnext · 79715390
      Bruce Momjian authored
      no longer returns buffer pointer, can be gotten from scan;
      	descriptor; bootstrap can create multi-key indexes;
      pg_procname index now is multi-key index; oidint2, oidint4, oidname
      are gone (must be removed from regression tests); use System Cache
      rather than sequential scan in many places; heap_modifytuple no
      longer takes buffer parameter; remove unused buffer parameter in
      a few other functions; oid8 is not index-able; remove some use of
      single-character variable names; cleanup Buffer variables usage
      and scan descriptor looping; cleaned up allocation and freeing of
      tuples; 18k lines of diff;
      79715390
  27. 26 Feb, 1998 1 commit
  28. 10 Feb, 1998 2 commits
  29. 31 Jan, 1998 1 commit
  30. 11 Dec, 1997 1 commit
  31. 25 Nov, 1997 1 commit
  32. 29 Sep, 1997 1 commit
  33. 26 Sep, 1997 1 commit
  34. 25 Sep, 1997 1 commit
  35. 24 Sep, 1997 2 commits