Skip to content

G
Gpdb

Greenplum / Gpdb

通知 7
Star 1
Fork 0
G
Gpdb

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

切换分支/标签
  1. 04 2月, 2018 1 次提交
  3. 03 2月, 2018 7 次提交
  5. 02 2月, 2018 10 次提交
    • D
      Fix documentation query · 83916dc1
      由 Daniel Gustafsson 提交于 
      Remove extra semicolon which breaks the query for copy-paste.

Per report by Michael Mulcahy
      83916dc1
    • D
      Fix typo in documentation and code comment · 1b1753da
      由 Daniel Gustafsson 提交于
      1b1753da
    • H
      Refactor handling of temporary files. · 8a257620
      由 Heikki Linnakangas 提交于 
      * Change the API of various functions that create temporary files so that
  the caller is not supposed to include the 'pgsql_tmp/' prefix in the
  pathname. This includes ExecWorkFile_CreateUnique, BufFileCreateFile
  (renamed to BufFileCreateTempFile to make that more clear), and
  BufFileOpenFile (also renamed, to BufFileOpenTempFile)

* The above-mentioned functions, which take an exact file name as argument,
  still don't obey temp_tablespaces. That's because it would make it
  unpredictable which exact path the file gets created in, which would make
  it hard to re-open the same file later. It is always created in the
  current database's pgsql_tmp diretory. (Normally, that's base/pgsql_tmp,
  but if the database's default tablespace is something else, then
  pgsql_tmp is also under that tablespace.)

* The OpenTemporaryFile() function now respects temp_tablespaces. We left
  that out when we merged with PG 8.3, because it was not applicable when
  we still had filespaces. The upstream commit that implemented this was
  acfce502.

The whole situation with temporary files is still a bit messy. Some
temporary files are created using the workfile API, while others are not.
The workfile code uses OpenNamedTemporaryFile() rather than
OpenTemporaryFile(), so they still don't obey temp_tablespaces. On the
other hand, the workfile code provides some extra features, like putting
limits on disk space and compression. Temporary files opened without the
workfile API still don't have those feature, even though they will now obey
temp_tablespaces. But this is a step in the right direction.
      8a257620
    • H
      Clean up the BufFile creation/opening API. · 7472c612
      由 Heikki Linnakangas 提交于 
      Rename BufFileCreateFile and BufFileOpenFile functions to
BufFileCreateNamedTemp and BufFileOpenNamedTemp. This makes it more clear
that these are for opening temporary files, not permantent ones, and the
"Named" means that they create/open a file with a particular name. Unlike
the upstream BufFileCreate() function, which constructs a unique filename
on the fly.

Remove the 'create' argument from BufFileOpenNamedTemp(). Previously, it
could be used to create a new file or open an existing file, now you must
use BufFileCreateNamedTemp() to create a new file, which seems more clear.

Remove BufFileCreateTemp_ReaderWriter() function, and replace its use
with BufFileCreateNamedTemp() and BufFileOpenNamedTemp(). It does the
same thing, and the Create/Open names seem more clear.
      7472c612
    • H
      Split OpenTemporaryFile into two versions, for clarity. · 4edf8cb8
      由 Heikki Linnakangas 提交于 
      OpenTemporaryFile() is now just like the upstream OpenTemporaryFile(),
except that it takes an extra filename prefix argument, for debugging
purposes. The files it creates are automatically made unique, and are
deleted on close.

OpenNamedTemporaryFile() creates a new file, or opens an existing file,
in the temp directory, with given name. This can be used for inter-process
communication.
      4edf8cb8
    • H
      Remove extra planner pass to remove "trivial" Result nodes. · c613cabf
      由 Heikki Linnakangas 提交于 
      Instead, avoid creating such Result nodes in the first place, by making
plan_pushdown_tlist() check if the Result node would have any work to do.

With this, you get Result nodes in some cases where the old code could zap
it away. But on the other hand, this can avoid inserting Result nodes, not
only on top of Appends, but on top of any node. This can be seen in the
included expected output changes: some test queries lose a Result, some
gain one. So performance-wise this is about a wash, but this is simpler.

The reason to do this right now is that we ran into issues with the
"zapping" code while working on the 9.0 merge. I'm sure we could fix those
issues, but let's do this rather than spend time debugging and fixing the
zapping code with the merge.
      c613cabf
    • J
      Make gprecoverseg full work for walrep · 6c3bb2e9
      由 Jimmy Yih 提交于 
      The gprecoverseg tool has been broken after filerep and persistent
tables were removed.  This commit cleans it up a little bit and makes
full mirror recovery work.  Also change mirror_promotion isolation2
test to use gprecoverseg tool instead of gpsegwalrep dev script.
      6c3bb2e9
    • M
      docs: pl/container fixes: (#4468) · 13fbf4ed
      由 Mel Kiyama 提交于 
      -Move note in Examples section to emphasize container ID depends on configuration
-Add creating a docker group in Docker Install instructions for CentOS 6
      13fbf4ed
    • A
      Vacuum fix for ERROR updated tuple is already HEAP_MOVED_OFF. · 313ab24f
      由 Ashwin Agrawal 提交于 
      `repair_frag()` should consult distributed snapshot
(`localXidSatisfiesAnyDistributedSnapshot()`) while following and moving chains
of updated tuples. Vacuum consults distributed snapshot
(`localXidSatisfiesAnyDistributedSnapshot()`) to find which tuples can be
deleted and not. For RECENTLY_DEAD tuples it used to make decision just based on
comparison with OldestXmin which is not sufficient and even there distributed
snapshot must be checked.

Fixes #4298
      313ab24f
    • L
      docs - pxf default port is now 5888 (#4452) · 14f6e4a4
      由 Lisa Owen 提交于
      14f6e4a4
  7. 01 2月, 2018 22 次提交