Hello Marina,
v9-0001-Pgbench-errors-use-the-RandomState-structure-for-.patch
- a patch for the RandomState structure (this is used to reset a client's
random seed during the repeating of transactions after serialization/deadlock
failures).
A few comments about this first patch.
Patch app
> Please cite actual instances of such reports. Vague queries like this help
nobody.
There were several questions on SO
https://stackoverflow.com/questions/49815460
https://stackoverflow.com/questions/47499766
https://stackoverflow.com/questions/47741077
https://dba.stackexchange.com/questions/1
On 9 June 2018 at 06:50, David Rowley wrote:
> It looks like this was 499be013de6, which was one of mine.
>
> A more simple case to reproduce is:
>
> drop table listp;
> create table listp (a int, b int) partition by list(a);
> create table listp1 partition of listp for values in (1);
> select * f
On Wed, Jun 06, 2018 at 12:37:00PM -0400, Alvaro Herrera wrote:
> On 2018-May-29, Michael Paquier wrote:
> If SCRAM channel binding is an important aspect to security, and the
> older OpenSSL versions will still be around in servers for some time
> yet, it seems like it behooves us to go the extra
On 06/08/2018 06:13 PM, Andrew Gierth wrote:
"Tom" == Tom Lane writes:
> Andrew Dunstan writes:
>> Please cite actual instances of such reports. Vague queries like
>> this help nobody.
We do also get them on the IRC channel every once in a while, not
very frequently but enough to not
On 2018-Jun-08, Alvaro Herrera wrote:
> Actually, the column order doesn't matter for a trigger function,
> because these don't refer to columns by number but by name. So unless
> users write trigger functions in C and use hardcoded column numbers
> (extremely unlikely), I think this is not an is
> "Tom" == Tom Lane writes:
> Andrew Dunstan writes:
>> Please cite actual instances of such reports. Vague queries like
>> this help nobody.
We do also get them on the IRC channel every once in a while, not
very frequently but enough to notice (maybe 2-3 so far this year?).
Tom> Unles
On 2018-Jun-07, Ashutosh Bapat wrote:
> On Thu, Jun 7, 2018 at 10:58 AM, Amit Langote
> wrote:
> > I don't understand why you think it's too troublesome to let the users
> > know that there is some way to use BR triggers with partitioning. We
> > didn't do that for indexes, for example, before
On 06/08/2018 04:54 PM, Steve Atkins wrote:
On Jun 8, 2018, at 1:47 PM, Tom Lane wrote:
Andrew Dunstan writes:
On 06/08/2018 04:34 PM, Steve Atkins wrote:
I've noticed a steady trickle of reports of postgresql servers being
compromised via being left available to the internet with insecu
I wrote:
> I'm inclined to think that auto-dereference is indeed a good idea,
> and am tempted to go make that change to make all this consistent.
> Comments?
Here's a draft patch for that. I ended up only changing
plperl_sv_to_datum. There is maybe a case for doing something
similar in plperl_r
> On Jun 8, 2018, at 1:47 PM, Tom Lane wrote:
>
> Andrew Dunstan writes:
>> On 06/08/2018 04:34 PM, Steve Atkins wrote:
>>> I've noticed a steady trickle of reports of postgresql servers being
>>> compromised via being left available to the internet with insecure or
>>> default configuration
Andrew Dunstan writes:
> On 06/08/2018 04:34 PM, Steve Atkins wrote:
>> I've noticed a steady trickle of reports of postgresql servers being
>> compromised via being left available to the internet with insecure or
>> default configuration, or brute-forced credentials. The symptoms are
>> random
On 06/08/2018 04:34 PM, Steve Atkins wrote:
I've noticed a steady trickle of reports of postgresql servers being
compromised via being left available to the internet with insecure or default
configuration, or brute-forced credentials. The symptoms are randomly named
binaries being uploaded
On 2018-Mar-01, Laurenz Albe wrote:
> I noticed that commit 25fff40798fc4ac11a241bfd9ab0c45c085e2212 forgot
> to teach SHOW ALL to show all GUCs when the user belongs to
> pg_read_all_settings.
>
> Patch attached; I think this should be backpatched.
Done, with the further fixes downthread. Tha
I've noticed a steady trickle of reports of postgresql servers being
compromised via being left available to the internet with insecure or default
configuration, or brute-forced credentials. The symptoms are randomly named
binaries being uploaded to the data directory and executed with the permi
On 6/8/18, 2:21 PM, "Andres Freund" wrote:
Not sure I quite understand what you mean. You're thinking of the case
where you're processing rows one-by-one with a cursor? Or that a single
spi call takes a long while to process the query?
The former, I believe. One example (lightly obfus
Andres Freund writes:
> Either way, I'm not convinced that handling query cancels in isolation
> is really the right thing. I think pretty much all forms of interrupt
> would need to be processed, not just cancels.
+1
regards, tom lane
On 2018-06-08 19:16:49 +, Peter Da Silva wrote:
> On 6/8/18, 1:12 PM, "Andres Freund" wrote:
> I'm not terribly opposed to this, but I wonder if the much more
> pragmatic solution is to just occasionally call a database function that
> checks this? You could just run SELECT 1 occa
On 6/8/18, 1:12 PM, "Andres Freund" wrote:
I'm not terribly opposed to this, but I wonder if the much more
pragmatic solution is to just occasionally call a database function that
checks this? You could just run SELECT 1 occasionally :/
After further discussion with our team:
Would
On 2018-Jun-08, Alvaro Herrera wrote:
> BTW a further bug here seems to be that "select * from pg_settings()"
> does not show the source file/line for members of the role, which seems
> to be documented to occur.
And I think this fixes it.
--
Álvaro Herrerahttps://www.2ndQuadran
On 2018-06-08 14:41:41 -0400, Tom Lane wrote:
> Andres Freund writes:
> > On 2018-06-08 18:08:14 +, Peter Da Silva wrote:
> >> There is a C-level variable QueryCancelPending that can be used to
> >> monitor for this case, but it’s not visible at the pl/tcl scripting
> >> level. This is a simpl
BTW a further bug here seems to be that "select * from pg_settings()"
does not show the source file/line for members of the role, which seems
to be documented to occur.
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Servi
Robert Haas writes:
> That being said, I don't mind a bit if you want to look for further
> speedups here, but if you do, keep in mind that a lot of queries won't
> even use partition-wise join, so all of the arrays will be of length
> 1. Even when partition-wise join is used, it is quite likely
On 6/8/18, 1:12 PM, "Andres Freund" wrote:
I'm not terribly opposed to this, but I wonder if the much more
pragmatic solution is to just occasionally call a database function that
checks this? You could just run SELECT 1 occasionally :/
That seems to work, and I suppose in most c
On Fri, Jun 8, 2018 at 2:10 PM, Tom Lane wrote:
>> I don't understand this complaint. Before, the code took one
>> AppendRelInfo, and according to you, it was clear what was supposed to
>> happen. Now it takes an array of AppendRelInfos and, according to
>> you, it's completely unclear. Yet tha
On 9 June 2018 at 04:57, Tom Lane wrote:
> Phil Florent writes:
>> explain analyze select * from v where v.k1 > date '2017-01-01';
>> ERREUR: XX000: did not find all requested child rels in append_rel_list
>> EMPLACEMENT : find_appinfos_by_relids, prepunion.c : 2643
>
> Reproduced here, thanks f
Andres Freund writes:
> On 2018-06-08 18:08:14 +, Peter Da Silva wrote:
>> There is a C-level variable QueryCancelPending that can be used to
>> monitor for this case, but it’s not visible at the pl/tcl scripting
>> level. This is a simple new command that returns the current state of
>> this
On 2018-Jun-09, David Rowley wrote:
> Of course, that could be fixed by adding something like "bool
> isinsert" to ExecConstraints(), so that it does not do the needless
> check on UPDATE,
Yeah, that was my actual suggestion rather than using Amit's patch
verbatim.
> but I'm strongly against the
On 2018-Jun-09, David Rowley wrote:
> Of course, that could be fixed by adding something like "bool
> isinsert" to ExecConstraints(), so that it does not do the needless
> check on UPDATE,
Yeah, that was my actual suggestion rather than using Amit's patch
verbatim.
> but I'm strongly against the
Hi,
On 2018-06-08 18:08:14 +, Peter Da Silva wrote:
> We have occasional need to run very long-running pl/tcl scripts. If
> the request is cancelled (say, by the user hitting ^c in psql) the
> server-side script still runs to completion.
>
> There is a C-level variable QueryCancelPending tha
Robert Haas writes:
> On Fri, Jun 8, 2018 at 12:56 AM, Tom Lane wrote:
>> The pre-v11 incarnation of those functions took a single AppendRelInfo,
>> specifying an exact translation from one parent relid to one child
>> relid. The fundamental problem I've got with the current code, entirely
>> in
We have occasional need to run very long-running pl/tcl scripts. If the request
is cancelled (say, by the user hitting ^c in psql) the server-side script still
runs to completion.
There is a C-level variable QueryCancelPending that can be used to monitor for
this case, but it’s not visible at t
On Wed, Jun 6, 2018 at 11:58 AM, Peter Eisentraut
wrote:
> --reflink={always,auto,never}. (This option name is adapted from GNU
...
> The setting always requires the use of relinks. If
Is it supposed to be relinks or reflinks? The two lines above don't agree.
--
Robert Haas
EnterpriseDB: ht
On Wed, Jun 6, 2018 at 12:08 PM, Alvaro Herrera
wrote:
> So, apparently this is not a Postgres 11 open item, but rather a bug
> that goes back to pg10. However, maybe it would be worth fixing soon
> anyway? In particular, if we want to perturb the explain output as
> suggested upthread, maybe *t
Hi,
On 2018-06-08 09:23:02 +0100, Simon Riggs wrote:
> I have also found another bug which affects what we do next.
>
> For context, AEL locks are normally removed by COMMIT or ABORT.
> StandbyReleaseOldLocks() is just a sweeper to catch anything that
> didn't send an abort before it died, so it
On 2018-06-08 11:29:17 +0530, Amit Kapila wrote:
> On Fri, Jun 8, 2018 at 2:55 AM, Andres Freund wrote:
> >
> > On 2018-06-07 14:19:18 -0700, Andres Freund wrote:
> > > We currently do acquire an xid when truncating the relation - but I
> > > think it'd somewhat fair to argue that that's somewhat
On 9 June 2018 at 04:52, Alvaro Herrera wrote:
> Truth is, the more I look at this, the more I think it should be done in
> the way Amit Langote was proposing: do away with the extra function, and
> check all those conditions inside ExecConstraints itself. We can add a
> new boolean tupleRouting
Melanie Plageman writes:
> On postgres built off of master on my mac (sierra), the following is the
> output:
[ scratches head ... ] I get the same results on either Mac or Linux:
regression=# create database u8 encoding utf8 template template0;
CREATE DATABASE
regression=# \c u8
You are now co
On Fri, Jun 8, 2018 at 4:55 AM, Amit Kapila wrote:
> On Fri, Jun 8, 2018 at 7:48 AM, Laurenz Albe
> wrote:
>
>> Amit Kapila wrote:
>> > On Wed, Jun 6, 2018 at 3:06 PM, Kuntal Ghosh <
>> kuntalghosh.2...@gmail.com> wrote:
>> > > It seems the "#ifndef FRONTEND" restriction was added around
>> > >
Phil Florent writes:
> explain analyze select * from v where v.k1 > date '2017-01-01';
> ERREUR: XX000: did not find all requested child rels in append_rel_list
> EMPLACEMENT : find_appinfos_by_relids, prepunion.c : 2643
Reproduced here, thanks for the report! This is very timely since
we were
On 2018-Jun-09, David Rowley wrote:
> On 9 June 2018 at 03:24, Alvaro Herrera wrote:
> > I was also wondering about introducing a new function call in this path
> > where previously was none. Given the amount of other stuff that's
> > happening when a tuple is inserted, I suppose it's not worth
>
> I did my test on 9.6.5 (Ubuntu 16.04) with:
>
> CREATE TABLE test_col (
> a text COLLATE "en_CA.utf8",
> b text COLLATE "en_US.utf8"
> );
> INSERT INTO test_col VALUES ('A', 'A');
> SELECT a < (SELECT 'foo'::text COLLATE "en_GB.utf8") FROM test_col;
>
> SQL Error: ERROR: could not det
On 9 June 2018 at 03:24, Alvaro Herrera wrote:
> I was also wondering about introducing a new function call in this path
> where previously was none. Given the amount of other stuff that's
> happening when a tuple is inserted, I suppose it's not worth worrying
> about in terms of making this an i
Melanie Plageman writes:
> In this case, why treat implicit and explicit collation conflicts
> differently?
Um ... because the SQL standard says so?
regards, tom lane
I wrote:
> ... So if we think that \undef ought to
> produce a SQL null, the thing to do is move the dereferencing loop to
> the beginning of plperl_sv_to_datum, and then \undef would produce NULL
> whether this transform is installed or not. I don't have a well-informed
> opinion on whether that'
On Fri, Jun 8, 2018 at 9:24 AM, Melanie Plageman
wrote:
> It seems like this would not allow the function/operator to decide if it
> cares about a determinate collation during execution, since it would
> already have errored out during planning.
>
In the case where the function/operator doesn't
On 8 June 2018 at 18:14, David Rowley wrote:
> On 8 June 2018 at 15:22, Tom Lane wrote:
>> David Rowley writes:
>>> On 8 June 2018 at 03:43, Tom Lane wrote:
Maybe there's something I'm missing here, but I sort of hoped that this
patch would nuke all the special-case code for Params in
> IIRC this was an intentional decision, made on the grounds that we
> can't tell whether the function/operator actually cares about having
> a determinate collation or not, so we have to leave it to execution of
> that function/operator to complain or not.
>
>
In this case, why treat implicit and
On Fri, Jun 8, 2018 at 9:12 AM, Melanie Plageman
wrote:
> I tried inserting data and did not get an error:
>
> CREATE TABLE test1 (
> a text COLLATE "de_DE",
> b text COLLATE "es_ES"
> );
>
> INSERT INTO test1 VALUES('b','b'), ('c','c'), ('g','g'), ('h','h');
> SELECT a < (select 'foo' CO
>
> Data, apparently...I got the same non-error result before inserting a
> record into test1 then I got the expected error.
>
> Its the function/operator the fails when faced with invalid input, not the
> planner, so the error requires data to provoke.
>
> David J.
>
>
>
I tried inserting data an
On 2018-Jun-07, David Rowley wrote:
> On 7 June 2018 at 15:57, Alvaro Herrera wrote:
> > Hm I was thinking this new function would be companion to ExecConstrains
> > (a fact I used in the name I proposed,) so it'd be in the same file
> > (probably right after it.)
>
> Okay. v5 (attached) does it
On Fri, Jun 8, 2018 at 12:56 AM, Tom Lane wrote:
> The pre-v11 incarnation of those functions took a single AppendRelInfo,
> specifying an exact translation from one parent relid to one child
> relid. The fundamental problem I've got with the current code, entirely
> independently of any performa
On Fri, Jun 8, 2018 at 1:52 AM, Tom Lane wrote
>
> I'm still of the opinion that find_appinfos_by_relids() needs to be
> nuked from orbit. It has nothing to recommend it either from the
> standpoint of performance or that of intellectual coherency (or maybe
> that problem is just inadequate docum
Hi,
I obtained an XX000 error testing my DSS application with PostgreSQL 11 beta 1.
Here is a simplified version of my test, no data in the tables :
-- 11
select version();
version
On Fri, Jun 8, 2018 at 3:24 AM, Owayss Kabtoul wrote:
> Hi folks,
>
> I ran into an issue where, on Postgres instances that have a very large
> number of databases per cluster (~15K), the autovacuum process seems to
> have a very high impact on CPU usage. Specifically, it is the autovacuum
> laun
On Fri, Jun 8, 2018 at 10:26 AM, Tom Lane wrote:
> David Rowley writes:
>> On 8 June 2018 at 08:22, Tom Lane wrote:
>>> I'm still of the opinion that find_appinfos_by_relids() needs to be
>>> nuked from orbit.
>
>> Yeah, I agree it's not nice that it pallocs an array then pfrees it
>> again. adj
Hello,
Sometimes I have to maintain two similar database and I have to update one
from the other and notice having the option to add ON CONFLICT DO NOTHING
clause to INSERT command in the dump data will allows pg_restore to be done
with free of ignore error.
The attache patch add --on-conflect-do
On 8 June 2018 at 11:33, Amit Kapila wrote:
> On Fri, Jun 8, 2018 at 1:53 PM, Simon Riggs wrote:
>>
>> So the attached patch fixes both the bug in the recent commit and the
>> one I just found by observation of 49bff5300d527, since they are
>> related.
>>
>> StandbyReleaseOldLocks() can sweep in
On Fri, Jun 8, 2018 at 2:23 PM, Dilip Kumar wrote:
> On Tue, Jun 5, 2018 at 8:03 PM, Amit Khandekar
> wrote:
>
>> Attached is a rebased patch version. Also included it in the upcoming
>> commitfest :
>> https://commitfest.postgresql.org/18/1660/
>>
>> In the rebased version, the new test cases a
On Fri, Jun 8, 2018 at 1:53 PM, Simon Riggs wrote:
>
> So the attached patch fixes both the bug in the recent commit and the
> one I just found by observation of 49bff5300d527, since they are
> related.
>
> StandbyReleaseOldLocks() can sweep in the same way as
> ExpireOldKnownAssignedTransactionId
On Tue, Jun 5, 2018 at 8:03 PM, Amit Khandekar
wrote:
> Attached is a rebased patch version. Also included it in the upcoming
> commitfest :
> https://commitfest.postgresql.org/18/1660/
>
> In the rebased version, the new test cases are added in the existing
> isolation/specs/partition-key-update
On 7 June 2018 at 22:25, Andres Freund wrote:
> On 2018-06-07 14:19:18 -0700, Andres Freund wrote:
> Look at:
>
> void
> ProcArrayApplyRecoveryInfo(RunningTransactions running)
> ...
> /*
> * Remove stale locks, if any.
> *
> * Locks are always assigned to the t
Hi folks,
I ran into an issue where, on Postgres instances that have a very large
number of databases per cluster (~15K), the autovacuum process seems to
have a very high impact on CPU usage. Specifically, it is the autovacuum
launcher process, not the workers. The launcher process eats a whole CP
63 matches
Mail list logo
