lp:postgresql

Created by Max Bowsher on 2011-01-03 and last modified on 2017-05-23
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 4 hours.

Last successful import was 1 hour ago.

Import started 1 hour ago on pear and finished 1 hour ago taking 1 minute — see the log
Import started 7 hours ago on pear and finished 7 hours ago taking 50 seconds — see the log
Import started 13 hours ago on pear and finished 13 hours ago taking 1 minute — see the log
Import started 19 hours ago on pear and finished 19 hours ago taking 1 minute — see the log
Import started on 2017-05-23 on pear and finished on 2017-05-23 taking 50 seconds — see the log
Import started on 2017-05-23 on pear and finished on 2017-05-23 taking 1 minute — see the log
Import started on 2017-05-23 on pear and finished on 2017-05-23 taking 1 minute — see the log
Import started on 2017-05-22 on pear and finished on 2017-05-22 taking 1 minute — see the log
Import started on 2017-05-22 on pear and finished on 2017-05-22 taking 1 minute — see the log
Import started on 2017-05-22 on russkaya and finished on 2017-05-22 taking 2 minutes — see the log

Recent revisions

42778. By Magnus Hagander 19 hours ago

Update URLs in pgindent source and README

Website and buildfarm is https, not http, and the ftp protocol will be
shut down shortly.

42777. By Heikki Linnakangas <email address hidden> on 2017-05-23

Verify that the server constructed the SCRAM nonce correctly.

The nonce consists of client and server nonces concatenated together. The
client checks the nonce contained the client nonce, but it would get fooled
if the server sent a truncated or even empty nonce.

Reported by Steven Fackler to <email address hidden>. Neither me or Steven
are sure what harm a malicious server could do with this, but let's fix it.

42776. By Michael Meskes <email address hidden> on 2017-05-23

Synced ecpg's pg_type.h with the one used in the backend.

Patch by Vinayak Pokale.

42775. By Magnus Hagander on 2017-05-22

Fix typo in comment

Author: Masahiko Sawada

42774. By Tom Lane <email address hidden> on 2017-05-21

Fix precision and rounding issues in money multiplication and division.

The cash_div_intX functions applied rint() to the result of the division.
That's not merely useless (because the result is already an integer) but
it causes precision loss for values larger than 2^52 or so, because of
the forced conversion to float8.

On the other hand, the cash_mul_fltX functions neglected to apply rint() to
their multiplication results, thus possibly causing off-by-one outputs.

Per C standard, arithmetic between any integral value and a float value is
performed in float format. Thus, cash_mul_flt4 and cash_div_flt4 produced
answers good to only about six digits, even when the float value is exact.
We can improve matters noticeably by widening the float inputs to double.
(It's tempting to consider using "long double" arithmetic if available,
but that's probably too much of a stretch for a back-patched fix.)

Also, document that cash_div_intX operators truncate rather than round.

Per bug #14663 from Richard Pistole. Back-patch to all supported branches.

Discussion: https://<email address hidden>

42773. By Tom Lane <email address hidden> on 2017-05-21

Fix contrib/sepgsql regression tests for partition NOT NULL change.

Commit 3ec76ff1f changed the partitioning logic to not install a forced
NOT NULL constraint on range partitioning columns. This affects the
expected output for contrib/sepgsql, because there's no longer LOG
entries reporting allowance of such a constraint. Per buildfarm.

42772. By Tom Lane <email address hidden> on 2017-05-21

Change documentation references to PG website to use https: not http:

This is more secure, and saves a redirect since we no longer accept
plain HTTP connections on the website.

References in code comments should probably be updated too, but
that doesn't seem to need back-patching, whereas this does.

Also, in the 9.2 branch, remove suggestion that you can get the
source code via FTP, since that service will be shut down soon.

Daniel Gustafsson, with a few additional changes by me

Discussion: https://<email address hidden>

42771. By Tom Lane <email address hidden> on 2017-05-19

Rethink flex flags for syncrep_scanner.l.

Using flex's -i switch to achieve case-insensitivity is not a very safe
practice, because the scanner's behavior may then depend on the locale
that flex was invoked in. In the particular example at hand, that's
not academic: the possible matches for "FIRST" will be different in a
Turkish locale than elsewhere. Do it the hard way instead, as our
other scanners do.

Also, drop use of -b -CF -p, because this scanner is only used when
parsing the contents of a GUC variable. That's not done often, and
the amount of text to be parsed can be expected to be trivial, so
prioritizing scanner speed over code size seems like quite the wrong
tradeoff. Using flex's default optimization options reduces the
size of syncrep_gram.o by more than 50%.

The case-insensitivity problem is new in HEAD (cf commit 3901fd70c).
The poor choice of optimization flags exists also in 9.6, but it doesn't
seem important enough to back-patch.

Discussion: https://<email address hidden>

42770. By Robert Haas <email address hidden> on 2017-05-19

pg_upgrade: Handle hash index upgrades more smoothly.

Mark any old hash indexes as invalid so that they don't get used, and
create a script to run REINDEX on all of them. Without this, we'd
still try to use any upgraded hash indexes, but it would fail.

Amit Kapila, reviewed by me. Per a suggestion from Tom Lane.

Discussion: http://<email address hidden>

42769. By Peter Eisentraut on 2017-05-19

Fix mistake in error message

Reported-by: tushar <email address hidden>
Author: Dilip Kumar <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.