lp:postgresql

Created by Max Bowsher on 2011-01-03 and last modified on 2017-12-12
Get this branch:
bzr branch lp:postgresql

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
VCS imports
Project:
PostgreSQL
Status:
Development

Import details

Import Status: Reviewed

This branch is an import of the HEAD branch of the Git repository at git://git.postgresql.org/git/postgresql.git.

The next import is scheduled to run in 3 hours.

Last successful import was 2 hours ago.

Import started 2 hours ago on pear and finished 2 hours ago taking 50 seconds — see the log
Import started 8 hours ago on pear and finished 8 hours ago taking 50 seconds — see the log
Import started 14 hours ago on pear and finished 14 hours ago taking 40 seconds — see the log
Import started 20 hours ago on pear and finished 20 hours ago taking 50 seconds — see the log
Import started on 2017-12-11 on pear and finished on 2017-12-11 taking 50 seconds — see the log
Import started on 2017-12-11 on pear and finished on 2017-12-11 taking 40 seconds — see the log
Import started on 2017-12-11 on russkaya and finished on 2017-12-11 taking 1 minute — see the log
Import started on 2017-12-11 on pear and finished on 2017-12-11 taking 40 seconds — see the log
Import started on 2017-12-10 on russkaya and finished on 2017-12-10 taking 1 minute — see the log
Import started on 2017-12-10 on pear and finished on 2017-12-10 taking 40 seconds — see the log

Recent revisions

43964. By Robert Haas <email address hidden> 6 hours ago

Remove bug from OPTIMIZER_DEBUG code for partition-wise join.

Etsuro Fujita, reviewed by Ashutosh Bapat

Discussion: http://<email address hidden>

43963. By Teodor Sigaev 10 hours ago

Make pg_trgm tests independ from standard_conforming_string. Tests uses
regular expression which contains backslash.

43962. By Peter Eisentraut on 2017-12-11

Fix comment

Reported-by: Noah Misch <email address hidden>

43961. By Tom Lane <email address hidden> on 2017-12-11

Fix corner-case coredump in _SPI_error_callback().

I noticed that _SPI_execute_plan initially sets spierrcontext.arg = NULL,
and only fills it in some time later. If an error were to happen in
between, _SPI_error_callback would try to dereference the null pointer.
This is unlikely --- there's not much between those points except
push-snapshot calls --- but it's clearly not impossible. Tweak the
callback to do nothing if the pointer isn't set yet.

It's been like this for awhile, so back-patch to all supported branches.

43960. By Robert Haas <email address hidden> on 2017-12-11

Improve comment about PartitionBoundInfoData.

Ashutosh Bapat, per discussion with Julien Rouhaund, who also
reviewed this patch.

Discussion: http://<email address hidden>

43959. By Tom Lane <email address hidden> on 2017-12-10

Stabilize output of new regression test case.

The test added by commit 390d58135 turns out to have different output
in CLOBBER_CACHE_ALWAYS builds: there's an extra CONTEXT line in the
error message as a result of detecting the error at a different place.
Possibly we should do something to make that more consistent. But as
a stopgap measure to make the buildfarm green again, adjust the test
to suppress CONTEXT entirely. We can revert this if we do something
in the backend to eliminate the inconsistency.

Discussion: https://<email address hidden>

43958. By Tom Lane <email address hidden> on 2017-12-09

Fix plpgsql to reinitialize record variables at block re-entry.

If one exits and re-enters a DECLARE ... BEGIN ... END block within a
single execution of a plpgsql function, perhaps due to a surrounding loop,
the declared variables are supposed to get re-initialized to null (or
whatever their initializer is). But this failed to happen for variables
of type "record", because while exec_stmt_block() expected such variables
to be included in the block's initvarnos list, plpgsql_add_initdatums()
only adds DTYPE_VAR variables to that list. This bug appears to have
been there since the aboriginal addition of plpgsql to our tree.

Fix by teaching plpgsql_add_initdatums() to include DTYPE_REC variables
as well. (We don't need to consider other DTYPEs because they don't
represent separately-stored values.) I failed to resist the temptation
to make some nearby cosmetic adjustments, too.

No back-patch, because there have not been field complaints, and it
seems possible that somewhere out there someone has code depending
on the incorrect behavior. In any case this change would have no
impact on correctly-written code.

Discussion: https://<email address hidden>

43957. By Magnus Hagander on 2017-12-09

Fix regression test output

Missed this in the last commit.

43956. By Magnus Hagander on 2017-12-09

Fix typo

Reported by Robins Tharakan

43955. By Noah Misch <email address hidden> on 2017-12-09

MSVC 2012+: Permit linking to 32-bit, MinGW-built libraries.

Notably, this permits linking to the 32-bit Perl binaries advertised on
perl.org, namely Strawberry Perl and ActivePerl. This has a side effect
of permitting linking to binaries built with obsolete MSVC versions.

By default, MSVC 2012 and later require a "safe exception handler table"
in each binary. MinGW-built, 32-bit DLLs lack the relevant exception
handler metadata, so linking to them failed with error LNK2026. Restore
the semantics of MSVC 2010, which omits the table from a given binary if
some linker input lacks metadata. This has no effect on 64-bit builds
or on MSVC 2010 and earlier. Back-patch to 9.3 (all supported
versions).

Reported by Victor Wagner.

Discussion: https://<email address hidden>

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.

Subscribers

No subscribers.