1. 05 Dec, 2002 1 commit
    • Tom Lane's avatar
      Phase 1 of read-only-plans project: cause executor state nodes to point · 1fd0c59e
      Tom Lane authored
      to plan nodes, not vice-versa.  All executor state nodes now inherit from
      struct PlanState.  Copying of plan trees has been simplified by not
      storing a list of SubPlans in Plan nodes (eliminating duplicate links).
      The executor still needs such a list, but it can build it during
      ExecutorStart since it has to scan the plan tree anyway.
      No initdb forced since no stored-on-disk structures changed, but you
      will need a full recompile because of node-numbering changes.
      1fd0c59e
  2. 04 Sep, 2002 1 commit
  3. 20 Jun, 2002 1 commit
  4. 06 Mar, 2002 1 commit
    • Bruce Momjian's avatar
      Change made to elog: · 92288a1c
      Bruce Momjian authored
      o  Change all current CVS messages of NOTICE to WARNING.  We were going
      to do this just before 7.3 beta but it has to be done now, as you will
      see below.
      
      o Change current INFO messages that should be controlled by
      client_min_messages to NOTICE.
      
      o Force remaining INFO messages, like from EXPLAIN, VACUUM VERBOSE, etc.
      to always go to the client.
      
      o Remove INFO from the client_min_messages options and add NOTICE.
      
      Seems we do need three non-ERROR elog levels to handle the various
      behaviors we need for these messages.
      
      Regression passed.
      92288a1c
  5. 01 Mar, 2002 1 commit
  6. 28 Oct, 2001 1 commit
  7. 25 Oct, 2001 1 commit
  8. 23 Mar, 2001 1 commit
  9. 22 Mar, 2001 2 commits
  10. 29 Jan, 2001 1 commit
    • Tom Lane's avatar
      Clean up handling of tuple descriptors so that result-tuple descriptors · 0d54d6ac
      Tom Lane authored
      allocated by plan nodes are not leaked at end of query.  This doesn't
      really matter for normal queries, but it sure does for queries invoked
      repetitively inside SQL functions.  Clean up some other grotty code
      associated with tupdescs, and fix a few other memory leaks exposed by
      tests with simple SQL functions.
      0d54d6ac
  11. 24 Jan, 2001 1 commit
  12. 13 Dec, 2000 1 commit
  13. 16 Nov, 2000 1 commit
  14. 12 Sep, 2000 1 commit
  15. 24 Aug, 2000 1 commit
  16. 12 Jul, 2000 1 commit
  17. 15 Jun, 2000 1 commit
  18. 26 Jan, 2000 1 commit
    • Bruce Momjian's avatar
      Add: · 5c25d602
      Bruce Momjian authored
        * Portions Copyright (c) 1996-2000, PostgreSQL, Inc
      
      to all files copyright Regents of Berkeley.  Man, that's a lot of files.
      5c25d602
  19. 19 Jan, 2000 1 commit
    • Tom Lane's avatar
      Fix handling of NULL constraint conditions: per SQL92 spec, a NULL result · 6d1efd76
      Tom Lane authored
      from a constraint condition does not violate the constraint (cf. discussion
      on pghackers 12/9/99).  Implemented by adding a parameter to ExecQual,
      specifying whether to return TRUE or FALSE when the qual result is
      really NULL in three-valued boolean logic.  Currently, ExecRelCheck is
      the only caller that asks for TRUE, but if we find any other places that
      have the wrong response to NULL, it'll be easy to fix them.
      6d1efd76
  20. 22 Nov, 1999 1 commit
  21. 17 Oct, 1999 1 commit
  22. 16 Oct, 1999 1 commit
  23. 24 Sep, 1999 1 commit
    • Tom Lane's avatar
      Several changes here, not very related but touching some of the same files. · e812458b
      Tom Lane authored
      * Buffer refcount cleanup (per my "progress report" to pghackers, 9/22).
      * Add links to backend PROC structs to sinval's array of per-backend info,
      and use these links for routines that need to check the state of all
      backends (rather than the slow, complicated search of the ShmemIndex
      hashtable that was used before).  Add databaseOID to PROC structs.
      * Use this to implement an interlock that prevents DESTROY DATABASE of
      a database containing running backends.  (It's a little tricky to prevent
      a concurrently-starting backend from getting in there, since the new
      backend is not able to lock anything at the time it tries to look up
      its database in pg_database.  My solution is to recheck that the DB is
      OK at the end of InitPostgres.  It may not be a 100% solution, but it's
      a lot better than no interlock at all...)
      * In ALTER TABLE RENAME, flush buffers for the relation before doing the
      rename of the physical files, to ensure we don't get failures later from
      mdblindwrt().
      * Update TRUNCATE patch so that it actually compiles against current
      sources :-(.
      You should do "make clean all" after pulling these changes.
      e812458b
  24. 16 Jul, 1999 1 commit
  25. 25 May, 1999 1 commit
  26. 10 May, 1999 1 commit
  27. 28 Feb, 1999 1 commit
  28. 24 Feb, 1999 1 commit
  29. 23 Feb, 1999 1 commit
  30. 22 Feb, 1999 1 commit
  31. 13 Feb, 1999 1 commit
  32. 03 Feb, 1999 1 commit
  33. 01 Sep, 1998 1 commit
  34. 19 Jul, 1998 2 commits
    • Bruce Momjian's avatar
      Remove un-needed psort close. · 4e6eb4ac
      Bruce Momjian authored
      4e6eb4ac
    • Bruce Momjian's avatar
      1) Queries using the having clause on base tables should work well · 460b20a4
      Bruce Momjian authored
         now. Here some tested features, (examples included in the patch):
      
      1.1) Subselects in the having clause 1.2) Double nested subselects
      1.3) Subselects used in the where clause and in the having clause
           simultaneously 1.4) Union Selects using having 1.5) Indexes
      on the base relations are used correctly 1.6) Unallowed Queries
      are prevented (e.g. qualifications in the
           having clause that belong to the where clause) 1.7) Insert
      into as select
      
      2) Queries using the having clause on view relations also work
         but there are some restrictions:
      
      2.1) Create View as Select ... Having ...; using base tables in
      the select 2.1.1) The Query rewrite system:
      
      2.1.2) Why are only simple queries allowed against a view from 2.1)
      ? 2.2) Select ... from testview1, testview2, ... having...; 3) Bug
      in ExecMergeJoin ??
      
      
      Regards Stefan
      460b20a4
  35. 15 Jun, 1998 2 commits
  36. 27 Feb, 1998 1 commit
  37. 26 Feb, 1998 1 commit