Skip to content

P
Postgres FD Implementation
Switch branch/tag
  1. 06 Mar, 2008 15 commits
  3. 05 Mar, 2008 10 commits
  5. 04 Mar, 2008 7 commits
    • Tom Lane's avatar
      Fix PREPARE TRANSACTION to reject the case where the transaction has dropped a · 7d6e6e2e
      Tom Lane authored 
      temporary table; we can't support that because there's no way to clean up the
source backend's internal state if the eventual COMMIT PREPARED is done by
another backend.  This was checked correctly in 8.1 but I broke it in 8.2 :-(.
Patch by Heikki Linnakangas, original trouble report by John Smith.
      7d6e6e2e
    • Magnus Hagander's avatar
      Use windows DACL fix for pg_regress as well. · 9b8a93ba
      Magnus Hagander authored 
      Dave Page
      9b8a93ba
    • Bruce Momjian's avatar
      Update pg_dump item: · 2c63d840
      Bruce Momjian authored 
      < 	  produce a single dump output file.
> 	  produce a single dump output file.  It also would require
> 	  several sessions to share the same snapshot.
      2c63d840
    • Bruce Momjian's avatar
      Show example of ts_headline() using a configuration name. · 27120522
      Bruce Momjian authored
      27120522
    • Bruce Momjian's avatar
      Remove: · 60c93d39
      Bruce Momjian authored 
      <
< 	o To better utilize resources, restore data, primary keys, and
<  	  indexes for a single table before restoring the next table
<
< 	  Hopefully this will allow the CPU-I/O load to be more uniform
< 	  for simultaneous restores.  The idea is to start data restores
< 	  for several objects, and once the first object is done, to move
< 	  on to its primary keys and indexes.  Over time, simultaneous
< 	  data loads and index builds will be running.
      60c93d39
    • Bruce Momjian's avatar
      Add URL for: · 66504d76
      Bruce Momjian authored 
              o Allow pg_restore to utilize multiple CPUs and I/O channels by
          restoring multiple objects simultaneously

> 	  http://archives.postgresql.org/pgsql-hackers/2008-02/msg00963.php
      66504d76
    • Bruce Momjian's avatar
      Add ideas for concurrent pg_dump and pg_restore: · a273d393
      Bruce Momjian authored 
      < * pg_dump
> * pg_dump / pg_restore
> 	o Allow pg_dump to utilize multiple CPUs and I/O channels by dumping
> 	  multiple objects simultaneously
>
> 	  The difficulty with this is getting multiple dump processes to
> 	  produce a single dump output file.
> 	  http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php
>
> 	o Allow pg_restore to utilize multiple CPUs and I/O channels by
>           restoring multiple objects simultaneously
>
> 	  This might require a pg_restore flag to indicate how many
> 	  simultaneous operations should be performed.  Only pg_dump's
> 	  -Fc format has the necessary dependency information.
>
> 	o To better utilize resources, restore data, primary keys, and
>  	  indexes for a single table before restoring the next table
>
> 	  Hopefully this will allow the CPU-I/O load to be more uniform
> 	  for simultaneous restores.  The idea is to start data restores
> 	  for several objects, and once the first object is done, to move
> 	  on to its primary keys and indexes.  Over time, simultaneous
> 	  data loads and index builds will be running.
>
> 	o To better utilize resources, allow pg_restore to check foreign
> 	  keys simultaneously, where possible
> 	o Allow pg_restore to create all indexes of a table
> 	  concurrently, via a single heap scan
>
> 	  This requires a pg_dump -Fc file because that format contains
>           the required dependency information.
> 	  http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php
>
> 	o Allow pg_restore to load different parts of the COPY data
> 	  simultaneously
<   single heap scan, and have a restore of a pg_dump somehow use it
>   single heap scan, and have pg_restore use it
<   http://archives.postgresql.org/pgsql-general/2007-05/msg01274.php
      a273d393
  7. 03 Mar, 2008 8 commits