Skip to content

G
Gpdb

Greenplum / Gpdb

通知 7
Star 1
Fork 0
G
Gpdb

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 30 6月, 2006 1 次提交
    • T
      Remove the separate 'stats buffer' process, letting backend stats messages · 51e400c9
      由 Tom Lane 提交于 
      be delivered directly to the collector process.  The extra process context
swaps required to transfer data through the buffer process seem to outweigh
any value the buffering might have.  Per recent discussion and tests.
I modified Bruce's draft patch to use poll() rather than select() where
available (this makes a noticeable difference on my system), and fixed
up the EXEC_BACKEND case.
      51e400c9
  3. 29 6月, 2006 4 次提交
  5. 28 6月, 2006 7 次提交
  7. 27 6月, 2006 5 次提交
    • B
      Add INCLUDING CONSTRAINTS to CREATE TABLE LIKE. · dc2c25fc
      由 Bruce Momjian 提交于 
      Greg Stark
      dc2c25fc
    • B
      Done: · 62f26936
      由 Bruce Momjian 提交于 
      < * %Disallow changing DEFAULT expression of a SERIAL column?
<
<   This should be done only if the existing SERIAL problems cannot be
<   fixed.
<
> * -Disallow changing DEFAULT expression of a SERIAL column
      62f26936
    • B
      Done: · 560feb47
      由 Bruce Momjian 提交于 
      > 	o -Add PQescapeIdentifier()
      560feb47
    • B
      Add PQescapeIdentifier() to libpq · 3b1790f9
      由 Bruce Momjian 提交于 
      Christopher Kings-Lynne
      3b1790f9
    • T
      Change the row constructor syntax (ROW(...)) so that list elements foo.* · ca0d2197
      由 Tom Lane 提交于 
      will be expanded to a list of their member fields, rather than creating
a nested rowtype field as formerly.  (The old behavior is still available
by omitting '.*'.)  This syntax is not allowed by the SQL spec AFAICS,
so changing its behavior doesn't violate the spec.  The new behavior is
substantially more useful since it allows, for example, triggers to check
for data changes with 'if row(new.*) is distinct from row(old.*)'.  Per
my recent proposal.
      ca0d2197
  9. 26 6月, 2006 3 次提交
  11. 25 6月, 2006 2 次提交
    • B
      Update entry: · ac7a126d
      由 Bruce Momjian 提交于 
      < * Allow heap reuse of UPDATEd rows if old and new versions are on the
<   same heap page?
> * Allow heap reuse of UPDATEd rows if no indexed columns are changed,
>   and old and new versions are on the same heap page?
<   This is possible for same-page updates because a single index row
<   can point to both old and new values.
>   While vacuum handles DELETEs fine, updating of non-indexed columns, like
>   counters, are difficult for VACUUM to handle efficiently.  This method
>   is possible for same-page updates because a single index row can be
>   used to point to both old and new values.
      ac7a126d
    • B
      Add UPDATE entry for row reuse. · fc6a2293
      由 Bruce Momjian 提交于 
      >
> * Allow heap reuse of UPDATEd rows if old and new versions are on the
>   same heap page?
>
>   This is possible for same-page updates because a single index row
>   can point to both old and new values.
>   http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
      fc6a2293
  13. 20 6月, 2006 1 次提交
  15. 19 6月, 2006 2 次提交
  17. 18 6月, 2006 1 次提交
  19. 17 6月, 2006 14 次提交