Permalink
Commits on Jun 14, 2012
  1. Add more message pluralization

    petere committed Jun 14, 2012
    Even though we can't do much about the case with multiple plurals in
    one sentence, we can fix the other cases.
  2. Improve readability and error messages in pg_backup_start_time.

    Robert Haas
    Robert Haas committed Jun 14, 2012
    Gurjeet Singh, with corrections by me.
  3. Doc corrections for pg_is_in_backup patch.

    Robert Haas
    Robert Haas committed Jun 14, 2012
    Fujii Masao
  4. New SQL functons pg_backup_in_progress() and pg_backup_start_time()

    Robert Haas
    Robert Haas committed Jun 14, 2012
    Darold Gilles, reviewed by Gabriele Bartolini and others, rebased by
    Marco Nenciarini.  Stylistic cleanup and OID fixes by me.
  5. During transaction cleanup, release locks before deleting files.

    Robert Haas
    Robert Haas committed Jun 14, 2012
    There's no need to hold onto the locks until the files are needed,
    and by doing it this way, we reduce the impact on other backends who
    may be awaiting locks we hold.
    
    Noah Misch
  6. Add new function log_newpage_buffer.

    Robert Haas
    Robert Haas committed Jun 14, 2012
    When I implemented the ginbuildempty() function as part of
    implementing unlogged tables, I falsified the note in the header
    comment for log_newpage.  Although we could fix that up by changing
    the comment, it seems cleaner to add a new function which is
    specifically intended to handle this case.  So do that.
  7. Remove misplaced sanity check from heap_create().

    Robert Haas
    Robert Haas committed Jun 14, 2012
    Even when allow_system_table_mods is not set, we allow creation of any
    type of SQL object in pg_catalog, except for relations.  And you can
    get relations into pg_catalog, too, by initially creating them in some
    other schema and then moving them with ALTER .. SET SCHEMA.  So this
    restriction, which prevents relations (only) from being created in
    pg_catalog directly, is fairly pointless.  If we need a safety mechanism
    for this, it should be placed further upstream, so that it affects all
    SQL objects uniformly, and picks up both CREATE and SET SCHEMA.
    
    For now, just rip it out, per discussion with Tom Lane.
  8. Remove RELKIND_UNCATALOGED.

    Robert Haas
    Robert Haas committed Jun 14, 2012
    This may have been important at some point in the past, but it no
    longer does anything useful.
    
    Review by Tom Lane.
  9. Make \conninfo print SSL information.

    Robert Haas
    Robert Haas committed Jun 14, 2012
    Alastair Turner, per suggestion from Bruce Momjian.
  10. Flesh out RELEASE_CHANGES instructions for branching in git.

    tglsfdc committed Jun 14, 2012
    We have this info in the wiki, but it should be here too.
  11. Stamp library minor versions for 9.3.

    tglsfdc committed Jun 14, 2012
    This includes fixing the MSVC copy of ecpg/preproc's version info, which
    seems to have been overlooked repeatedly.  Can't we fix that so there are
    not two copies??
  12. Stamp HEAD as 9.3devel.

    tglsfdc committed Jun 14, 2012
    Let the hacking begin ...
Commits on Jun 13, 2012
  1. Revisit error message details for JSON input parsing.

    tglsfdc committed Jun 13, 2012
    Instead of identifying error locations only by line number (which could
    be entirely unhelpful with long input lines), provide a fragment of the
    input text too, placing this info in a new CONTEXT entry.  Make the
    error detail messages conform more closely to style guidelines, fix
    failure to expose some of them for translation, ensure compiler can
    check formats against supplied parameters.
  2. Revert "Reduce checkpoints and WAL traffic on low activity database s…

    tglsfdc committed Jun 13, 2012
    …erver"
    
    This reverts commit 18fb9d8.  Per
    discussion, it does not seem like a good idea to allow committed changes to
    go un-checkpointed indefinitely, as could happen in a low-traffic server;
    that makes us entirely reliant on the WAL stream with no redundancy that
    might aid data recovery in case of disk failure.
    
    This re-introduces the original problem of hot-standby setups generating a
    small continuing stream of WAL traffic even when idle, but there are other
    ways to address that without compromising crash recovery, so we'll revisit
    that issue in a future release cycle.
  3. Fix description of SQL-standard meaning of CREATE LOCAL TEMP TABLE.

    tglsfdc committed Jun 13, 2012
    I had this slightly wrong, as noted by Noah Misch.
  4. Deprecate use of GLOBAL and LOCAL in temp table creation.

    tglsfdc committed Jun 13, 2012
    Aside from adjusting the documentation to say that these are deprecated,
    we now report a warning (not an error) for use of GLOBAL, since it seems
    fairly likely that we might change that to request SQL-spec-compliant temp
    table behavior in the foreseeable future.  Although our handling of LOCAL
    is equally nonstandard, there is no evident interest in ever implementing
    SQL modules, and furthermore some other products interpret LOCAL as
    behaving the same way we do.  So no expectation of change and no warning
    for LOCAL; but it still seems a good idea to deprecate writing it.
    
    Noah Misch
  5. Support Linux's oom_score_adj API as well as the older oom_adj API.

    tglsfdc committed Jun 13, 2012
    The simplest way to handle this is just to copy-and-paste the relevant
    code block in fork_process.c, so that's what I did. (It's possible that
    something more complicated would be useful to packagers who want to work
    with either the old or the new API; but at this point the number of such
    people is rapidly approaching zero, so let's just get the minimal thing
    done.)  Update relevant documentation as well.
  6. In pg_upgrade, verify that the install user has the same oid on both

    bmomjian committed Jun 13, 2012
    clusters, and make sure the new cluster has no additional users.
    
    Backpatch to 9.1.
  7. Improve documentation of postgres -C option

    petere committed Jun 13, 2012
    Clarify help (s/return/print/), and explain that this option is for
    use by other programs, not for user-facing use (it does not print
    units).
Commits on Jun 12, 2012
  1. Minor code review for json.c.

    tglsfdc committed Jun 12, 2012
    Improve commenting, conform to project style for use of ++ etc.
    No functional changes.
  2. Mark JSON error detail messages for translation.

    Robert Haas
    Robert Haas committed Jun 12, 2012
    Per gripe from Tom Lane.
  3. Copy-editing of release notes.

    Robert Haas
    Robert Haas committed Jun 12, 2012
    Remove a couple of items that were actually back-patched bug fixes.
    Add additional details to a couple of items which lacked a description.
    Improve attributions for a couple of items I was involved with.
    A few other miscellaneous corrections.
  4. Ensure pg_ctl behaves sanely when data directory is not specified.

    tglsfdc committed Jun 12, 2012
    Commit aaa6e1d introduced multiple hazards
    in the case where pg_ctl is executed with neither a -D switch nor any
    PGDATA environment variable.  It would dump core on machines which are
    unforgiving about printf("%s", NULL), or failing that possibly give a
    rather unhelpful complaint about being unable to execute "postgres -C",
    rather than the logically prior complaint about not being told where the
    data directory is.
    
    Edmund Horner's report suggests that there is another, Windows-specific
    hazard here, but I'm not the person to fix that; it would in any case only
    be significant when trying to use a config-only PGDATA pointer.
  5. Fix pg_dump output to a named tar-file archive.

    tglsfdc committed Jun 12, 2012
    "pg_dump -Ft -f filename ..." got broken by my recent commit
    4317e02, which I fear I only tested
    in the output-to-stdout variant.
    
    Report and fix by Muhammad Asif Naeem.
Commits on Jun 11, 2012
  1. pg_receivexlog: Rename option --dir to --directory

    petere committed Jun 11, 2012
    getopt_long() allows abbreviating long options, so we might as well
    give the option the full name, and users can abbreviate it how they
    like.
    
    Do some general polishing of the --help output at the same time.
  2. Prevent non-streaming replication connections from being selected syn…

    mhagander committed Jun 11, 2012
    …c slave
    
    This prevents a pg_basebackup backup session that just does a base
    backup (no xlog involved at all) from becoming the synchronous slave
    and thus blocking all access while it runs.
    
    Also fixes the problem when a higher priority slave shows up it would
    become the sync standby before it has reached the STREAMING state, by
    making sure we can only switch to a walsender that's actually STREAMING.
    
    Fujii Masao
  3. Revert behaviour of -x/--xlog to 9.1 semantics

    mhagander committed Jun 10, 2012
    To replace it, add -X/--xlog-method that allows the specification
    of fetch or stream.
    
    Do this to avoid unnecessary backwards-incompatiblity. Spotted and
    suggested by Peter Eisentraut.
Commits on Jun 10, 2012
  1. Fix pg_basebackup/pg_receivexlog for floating point timestamps

    mhagander committed Jun 10, 2012
    Since the replication protocol deals with TimestampTz, we need to
    care for the floating point case as well in the frontend tools.
    
    Fujii Masao, with changes from Magnus Hagander