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

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    changing semantics too much.  statement_timestamp is now set immediately
    upon receipt of a client command message, and the various places that used
    to do their own gettimeofday() calls to mark command startup are referenced
    to that instead.  I have also made stats_command_string use that same
    value for pg_stat_activity.query_start for both the command itself and
    its eventual replacement by <IDLE> or <idle in transaction>.  There was
    some debate about that, but no argument that seemed convincing enough to
    justify an extra gettimeofday() call.
    27c3e3de
    History
    Name Last commit Last update