Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

drop_database.sgml

Blame
    • Bruce Momjian's avatar
      11023eb1
      Meanwhile, database names with single quotes in names don't work very well · 11023eb1
      Bruce Momjian authored
      at all, and because of shell quoting rules this can't be fixed, so I put
      in error messages to that end.
      
      Also, calling create or drop database in a transaction block is not so
      good either, because the file system mysteriously refuses to roll back rm
      calls on transaction aborts. :) So I put in checks to see if a transaction
      is in progress and signal an error.
      
      Also I put the whole call in a transaction of its own to be able to roll
      back changes to pg_database in case the file system operations fail.
      
      The alternative location issues I posted recently were untouched, awaiting
      the outcome of that discussion. Other than that, this should be much more
      fool-proof now.
      
      The docs I cleaned up as well.
      
      Peter Eisentraut                  Sernanders väg 10:115
      11023eb1
      History
      Meanwhile, database names with single quotes in names don't work very well
      Bruce Momjian authored
      at all, and because of shell quoting rules this can't be fixed, so I put
      in error messages to that end.
      
      Also, calling create or drop database in a transaction block is not so
      good either, because the file system mysteriously refuses to roll back rm
      calls on transaction aborts. :) So I put in checks to see if a transaction
      is in progress and signal an error.
      
      Also I put the whole call in a transaction of its own to be able to roll
      back changes to pg_database in case the file system operations fail.
      
      The alternative location issues I posted recently were untouched, awaiting
      the outcome of that discussion. Other than that, this should be much more
      fool-proof now.
      
      The docs I cleaned up as well.
      
      Peter Eisentraut                  Sernanders väg 10:115