Hello
Currently log_autovacuum_min_duration log message has no difference between
regular autovacuum and to prevent wraparound autovacuum. There are important
differences, for example, backend can automatically cancel regular autovacuum,
but not anti-wraparound. I think it is useful indicate ant
Isaac Morland writes:
>>> It would also provide a *very* fertile source of shell-script-injection
>>> vulnerabilities. (Whaddya mean, you tried to use a user name with a
>>> quote mark in it?)
> If I understand the proposal correctly, the pgpass program would run on the
> client, invoked by libp
On Mon, Jul 9, 2018 at 4:40 PM, Andres Freund wrote:
> FWIW, I've lately noticed that I spend a fair time waiting for the
> linker during edit-compile-test cycles. Due to an independent issue I
> just used the gold linker, and the speedup is quite noticable.
>
> Just relinking the backend, withou
On 20 July 2018 at 17:22, Tels wrote:
> Moin,
>
> > It would also provide a *very* fertile source of shell-script-injection
> > vulnerabilities. (Whaddya mean, you tried to use a user name with a
> > quote mark in it?)
>
> Little Bobby Tables, we call him. :)
>
> I'm also concerned that that wou
Thomas,
Thanks for your offer to run some tests on different OSes and filesystems
that you have. Anything you can provide here would be much appreciated. I
don't have anything other than our native SmartOS/ZFS based configurations,
but I might be able to setup some VMs and get results that way. I
On Fri, Jul 20, 2018 at 2:17 AM, Jeremy Schneider
wrote:
> I'd like to bump this old bug that Lloyd filed for more discussion. It
> seems serious enough to me that we should at least talk about it.
>
> Anyone with simply the login privilege and the ability to run SQL can
> instantly block all new
Peter,
Thanks for your feedback. I'm happy to change the name of the tunable or to
update the man page in any way. I have already posted an updated patch
with changes to the man page which I think may address your concerns there,
but please let me know if that still needs more work. It looks like
On Fri, Jul 20, 2018 at 1:54 AM Heikki Linnakangas wrote:
> On 19/07/18 23:13, Andres Freund wrote:
> > On 2018-07-19 14:54:52 -0500, Nico Williams wrote:
> >> On Thu, Jul 19, 2018 at 12:20:53PM -0700, Andres Freund wrote:
> >>> On 2018-07-19 11:57:25 +0300, Heikki Linnakangas wrote:
> Ugh.
Hi Robert,
I'm new to the Postgresql community, so I'm not familiar with how patches
are accepted here. Thanks for your detailed explanation. I do want to keep
pushing on this. I'll respond separately to Peter and to Tomas regarding
their emails.
Thanks again,
Jerry
On Wed, Jul 18, 2018 at 1:43
11.07.2018 17:01, Ashutosh Bapat пишет:
> The patch still applies and it's part of this commitfest.
>
> On Tue, Oct 3, 2017 at 8:36 PM, Sokolov Yura wrote:
>> On 2017-10-03 17:30, Sokolov Yura wrote:
>>>
>>> Good day, hackers.
>>>
>>> During hard workload sometimes process reaches deadlock timeou
Moin,
On Wed, July 18, 2018 7:25 pm, Tom Lane wrote:
> Alvaro Herrera writes:
>> Seems to me that passing %-specifiers to the command would make it more
>> useful (%u for "user", "host" etc) -- your command could refuse to give
>> you a password for the superuser account for instance but grant on
Moin,
On Fri, July 20, 2018 10:55 am, Victor Wagner wrote:
> On Fri, 20 Jul 2018 10:25:47 -0400
> Tom Lane wrote:
>
>> Victor Wagner writes:
>> > I've discovered that in the branch REL_11_STABLE there is shell
>> > script src/bin/pg_upgrade/test.sh which doesn't work under Solaris
>> > 10. (it u
> On 20 Jul 2018, at 17:34, Tom Lane wrote:
>
> Heikki Linnakangas writes:
>> No objections, if you want to make the effort. But IMHO the lseek+read
>> fallback is good enough on Windows. Unless you were thinking that we
>> could then remove the !HAVE_PREAD fallback altogether. Are there any
Hi,
On 2018-07-20 16:43:33 -0400, Tom Lane wrote:
> Andres Freund writes:
> > On 2018-07-20 15:35:39 -0400, Tom Lane wrote:
> >> In any case, I strongly resist making performance-based changes on
> >> the basis of one test on one kernel and one hardware platform.
>
> > Sure, it'd be good to do m
Andres Freund writes:
> On 2018-07-20 15:35:39 -0400, Tom Lane wrote:
>> In any case, I strongly resist making performance-based changes on
>> the basis of one test on one kernel and one hardware platform.
> Sure, it'd be good to do more of that. But from a theoretical POV it's
> quite logical th
On 2018-07-20 16:15:14 -0400, Tom Lane wrote:
> We've seen several occurrences of $subject in the buildfarm in the past
> month or so. Scraping the logs, I find
>
> coypu| 2018-06-14 21:17:49 | HEAD | Check | 2018-06-14
> 23:31:44.505 CEST [5b22deb8.30e1:124] ERROR: could not read
On 01/03/18 12:40, Heikki Linnakangas wrote:
On 16/01/18 15:00, Yoshimi Ichiyanagi wrote:
These patches enable to use Persistent Memory Development Kit(PMDK)[1]
for reading/writing WAL logs on persistent memory(PMEM).
PMEM is next generation storage and it has a number of nice features:
fast, by
We've seen several occurrences of $subject in the buildfarm in the past
month or so. Scraping the logs, I find
coypu| 2018-06-14 21:17:49 | HEAD | Check | 2018-06-14
23:31:44.505 CEST [5b22deb8.30e1:124] ERROR: could not read block 3 in file
"base/16384/2662": read only 0 of 8192
On 2018-07-20 15:35:39 -0400, Tom Lane wrote:
> Andres Freund writes:
> > On 2018-07-21 00:53:28 +0530, Mithun Cy wrote:
> >> I did a quick test applying the patch with same settings as initial mail I
> >> have reported (On postgresql 10 latest code)
> >> 72 clients
> >>
> >> CASE 1:
> >> Withou
Andres Freund writes:
> On 2018-07-21 00:53:28 +0530, Mithun Cy wrote:
>> I did a quick test applying the patch with same settings as initial mail I
>> have reported (On postgresql 10 latest code)
>> 72 clients
>>
>> CASE 1:
>> Without Patch : TPS 29269.823540
>>
>> With Patch : TPS 36005.54496
Something like this?
Thank you.
logical-replication-worker-insert.patch
Description: Binary data
Hi,
On 2018-07-21 00:53:28 +0530, Mithun Cy wrote:
> On Fri, Jul 20, 2018 at 10:52 AM, Thomas Munro <
> thomas.mu...@enterprisedb.com> wrote:
>
> > On Fri, Jul 20, 2018 at 7:56 AM, Tom Lane wrote:
> > >
> > > It's not *that* noticeable, as I failed to demonstrate any performance
> > > difference
On Fri, Jul 20, 2018 at 10:52 AM, Thomas Munro <
thomas.mu...@enterprisedb.com> wrote:
> On Fri, Jul 20, 2018 at 7:56 AM, Tom Lane wrote:
> >
> > It's not *that* noticeable, as I failed to demonstrate any performance
> > difference before committing the patch. I think some more investigation
> >
On 2018-Jul-19, Quan TRAN wrote:
> Hello,
>
> In worker.c:
>
> - in apply_handle_insert, slot_store_cstrings is called before
> PushActiveSnapshot
> - in apply_handle_update & apply_handle_delete, slot_store_cstrings is
> called after PushActiveSnapshot
>
> /* Process and store
On Wed, Jul 18, 2018 at 09:28:19AM +0200, Kaye Ann Ignacio wrote:
> I'm trying to add a foreign constraint in my local table to reference a
> column in a materialized view, is it possible to alter this materialized
> view by adding a primary key constraint?
It's not, but I'm working on a patch for
The following review has been posted through the commitfest application:
make installcheck-world: tested, passed
Implements feature: tested, passed
Spec compliant: not tested
Documentation:not tested
This patch applied cleanly and worked as expected.
Patch description
Hi,
I'm trying to add a foreign constraint in my local table to reference a
column in a materialized view, is it possible to alter this materialized
view by adding a primary key constraint?
Thank you.
--
Kaye Ann Ignacio, Programmer
proceedit "the BPaaS company"
kaye.igna...@proceedit.com +34 6
On Thu, Jul 19, 2018 at 4:29 AM, Masahiko Sawada wrote:
>> One area that might be worth investigating is retail index tuple
>> deletion performed within the executor in the event of non-HOT
>> updates. Maybe LP_REDIRECT could be repurposed to mean "ghost record",
>> at least in unique index tuples
On 12/07/18 16:08, Michael Paquier wrote:
On Thu, Jul 12, 2018 at 12:34:51PM +0300, Heikki Linnakangas wrote:
Hmm. That is actually in a section called "Default Channel Binding". And the
first paragraph says "A default channel binding type agreement process for
all SASL application protocols tha
Hi,
On 2018-07-20 08:27:34 -0400, Robert Haas wrote:
> On Thu, Jul 19, 2018 at 4:32 PM, Andres Freund wrote:
> >> 1. Why the error message changes? If there's a good reason, it should
> >> be done as a separate commit, or at least well-documented in the
> >> commit message.
> >
> > Because there
Heikki Linnakangas writes:
> No objections, if you want to make the effort. But IMHO the lseek+read
> fallback is good enough on Windows. Unless you were thinking that we
> could then remove the !HAVE_PREAD fallback altogether. Are there any
> other platforms out there that don't have pread/pwr
On Wed, Jul 18, 2018 at 4:38 AM, Tsunakawa, Takayuki
wrote:
> IIRC, the pop up doesn't appear under Windows service. If you start the
> database server with pg_ctl start on the command prompt, the pop up will
> appear, which I think is not bad.
Hmm. I think that might be bad. What makes you
On Fri, Jul 20, 2018 at 8:38 AM, Robert Haas wrote:
> This looks like a terrible design to me. If somebody in future
> invents a new plan type that is not projection-capable, then this
> could fail an assertion here and there won't be any simple fix. And
> if you reach here and the child targetl
On 20 July 2018 at 21:44, Amit Langote wrote:
> But I don't think the result of make_partition_pruneinfo itself has to be
> List of PartitionedRelPruneInfo nested under PartitionPruneInfo. I gather
> that each PartitionPruneInfo corresponds to each root partitioned table
> and a PartitionedRelPru
Victor Wagner writes:
> Tom Lane wrote:
>> Please send a patch. Most of us do not have access to old shells
> Here it goes. Previous letter was written before fixed tests were
> completed, because this old machine is slow.
Thanks. Will check on my own dinosaurs, and push if I don't find
a pro
On 2018-07-20 11:53:32 +0300, Heikki Linnakangas wrote:
> ISTM that no-one has any great ideas on what to do about the ereport() in
> quickdie().
I think we actually have some decent ideas how to make that less
problematic in a number of cases. Avoid translation (thereby avoiding
direct malloc())
On 2018-07-20 12:13:19 +0530, Nikhil Sontakke wrote:
> Hi Andres,
>
>
> > So what if we, at the begin / end of cache miss handling, re-check if
> > the to-be-decoded transaction is still in-progress (or has
> > committed). And we throw an error if that happened. That error is then
> > caught in reo
(This email seemed to only come to me and somehow missed the mailing
list. Including the message here in its entirety)
On 20 July 2018 at 13:26, Karen Huddleston wrote:
> The following review has been posted through the commitfest application:
> make installcheck-world: tested, passed
> Impleme
On Fri, 20 Jul 2018 10:25:47 -0400
Tom Lane wrote:
> Victor Wagner writes:
> > I've discovered that in the branch REL_11_STABLE there is shell
> > script src/bin/pg_upgrade/test.sh which doesn't work under Solaris
> > 10. (it uses $(command) syntax with is not compatible with original
> > Solari
Yugo Nagata writes:
> Recently, one of our clients reported a problem that Windows 10 sometime
> (approximately once in 300 tries) hung up at OS starting up while PostgreSQL
> 9.3.x service is starting up. My co-worker analyzed this and found that
> PostgreSQL's auxiliary process and Windows' log
Victor Wagner writes:
> I've discovered that in the branch REL_11_STABLE there is shell script
> src/bin/pg_upgrade/test.sh which doesn't work under Solaris 10.
> (it uses $(command) syntax with is not compatible with original
> Solaris /bin/sh)
OK ...
> It is quite easy to replace $() syntax wi
Collegues,
I've discovered that in the branch REL_11_STABLE there is shell script
src/bin/pg_upgrade/test.sh which doesn't work under Solaris 10.
(it uses $(command) syntax with is not compatible with original
Solaris /bin/sh)
I was quite surprised that this problem goes unnoticed on big buildfar
On Wed, Jul 18, 2018 at 8:00 AM, Etsuro Fujita
wrote:
> [ new patch ]
+ /*
+ * If the child plan is an Append or MergeAppend, the targetlists of its
+ * subplans would have already been adjusted before we get here, so need
+ * to work here.
+ */
+ if (IsA(subplan, Append) || IsA(subplan, MergeApp
On Thu, Jul 19, 2018 at 4:32 PM, Andres Freund wrote:
>> 1. Why the error message changes? If there's a good reason, it should
>> be done as a separate commit, or at least well-documented in the
>> commit message.
>
> Because there's a lot of "invalid input syntax for type %s: \"%s\"",
> error me
Hi Amit,
On 07/19/2018 10:27 PM, Amit Langote wrote:
On 2018/07/19 23:18, Jesper Pedersen wrote:
I'm thinking about how to best use these functions to generate a graph
that represents the partition hierarchy.
What about renaming pg_partition_tree_tables() to pg_partition_children(),
and have i
Hi, Aleksandr!
On Mon, Jul 9, 2018 at 10:26 AM Aleksandr Parfenov <
a.parfe...@postgrespro.ru> wrote:
> A new version of the patch in the attachment. There are no changes since
> the last version except refreshing it to current HEAD.
>
I took a look at this patch. It applied cleanly, but didn't
On Fri, Jul 20, 2018 at 05:58:13PM +0900, Yugo Nagata wrote:
> He reported this problem to pgsql-general list as below. Also, he created a
> patch
> to add a build-time option for adding 0.5 or 3.0 seconds delay after each sub
> process starts. The attached is the same one. Our client confirmed
On 2018/07/19 22:03, David Rowley wrote:
> v3-0001-Fix-run-time-partition-pruning-for-UNION-ALL-pare.patch
Thanks for updating the patch.
I studied this patch today and concluded that it's going a bit too far by
carrying the nested partition pruning info structures from the planner all
the way in
Hello Charles,
> Here is my current working status.
> 1. Complete the thrift_binary_in and thrift_binary_out functions, so
> that users can express their thrift struct using json. These two
> functions support both simple data struct and complex data structure
> like struct and map. 2. added t
Hello PostgreSQL Community!
Not long ago I faced the situation concerning ODBC/libpq client hanging in
case of some network problems.
I had a discussion regarding this issue within pgsql-o...@postgresql.org
and got some suggestions.
Here is this discussion:
https://www.postgresql.org/message-id
Hi,
Recently, one of our clients reported a problem that Windows 10 sometime
(approximately once in 300 tries) hung up at OS starting up while PostgreSQL
9.3.x service is starting up. My co-worker analyzed this and found that
PostgreSQL's auxiliary process and Windows' logon processes are in a de
(2018/07/20 13:49), Michael Paquier wrote:
On Thu, Jul 19, 2018 at 05:35:11PM +0900, Etsuro Fujita wrote:
+1 for the general idea. (Actually, I also thought the same thing before.)
But since this is definitely a matter of PG12, ISTM that it's wise to work
on this after addressing the issue in [
On 19/07/18 23:13, Andres Freund wrote:
On 2018-07-19 14:54:52 -0500, Nico Williams wrote:
On Thu, Jul 19, 2018 at 12:20:53PM -0700, Andres Freund wrote:
On 2018-07-19 11:57:25 +0300, Heikki Linnakangas wrote:
Ugh. Yeah, in wal_quickdie, and other aux process *_quickdie() handlers, I
agree we
On 19/07/18 23:04, Nico Williams wrote:
On Thu, Jun 22, 2017 at 03:10:31PM -0400, Tom Lane wrote:
Andres Freund writes:
Or, probably more robust: Simply _exit(2) without further ado, and rely
on postmaster to output an appropriate error message. Arguably it's not
actually useful to see hundred
On Thu, Jul 12, 2018 at 01:55:31PM +1200, Thomas Munro wrote:
> A couple of years ago, Oskari Saarenmaa proposed a patch[1] to adopt
> $SUBJECT. Last year, Tobias Oberstein argued again that we should do
> that[2]. At the end of that thread there was a +1 from multiple
> committers in support of
On 20/07/18 01:50, Thomas Munro wrote:
An idea for how to handle Windows, in a follow-up patch: add a file
src/backend/port/win32/file.c that defines pgwin32_pread() and
pgwin32_pwrite(), wrapping WriteFile()/ReadFile() and passing in an
"OVERLAPPED" struct with the offset and sets errno on error
56 matches
Mail list logo
