On Wed, Jun 17, 2015 at 3:17 PM, Michael Paquier
wrote:
> As pointed by dev1ant on the original bug report, process_remote_file
> should ignore files named as pg_xlog/xlogtemp.*, and I think that this
> is the right thing to do. Any objections for a patch that at the same
> time makes "xlogtemp."
Hello,
Here is version 3, including many performance tests with various settings,
representing about 100 hours of pgbench run. This patch aims at improving
checkpoint I/O behavior so that tps throughput is improved, late
transactions are less frequent, and overall performances are more stabl
Hi all,
I just bumped into this report regarding pg_rewind, that impacts as
well the version shipped in src/bin/pg_rewind:
https://github.com/vmware/pg_rewind/issues/45
In short, the issue refers to the fact that if the source server
filemap includes xlogtemp files pg_rewind will surely fail with
On Thu, Dec 11, 2014 at 10:24:20AM -0800, Jeff Janes wrote:
> On Thu, Dec 11, 2014 at 8:03 AM, Tom Lane wrote:
> > 2. The amount of pre-release testing we get from people outside the
> > hard-core development crowd seems to be continuing to decrease.
> > We were fortunate that somebody found the J
Hi,
Currently the issue is easily reproducible. Steps to reproduce:
* Set some aggressive values for auto-vacuuming.
* Run a heavy database update/delete/insert queries. This leads to invoking
auto-vacuuming in quick successions.
* Change the system time to older for eg. 1995-01-01
Suddenly auto-
On Tue, Jun 16, 2015 at 1:08 PM, Xiaoyulei wrote:
> In XidInMVCCSnapshot, it will check xid from tuple if is in snapshot->subxip.
> It means tuple store subtransaction?
Tuple stores only the transaction id related to the operation. This
can be either main transaction id or sub transaction id.
>
On Wed, Jun 17, 2015 at 6:58 AM, Alvaro Herrera
wrote:
> Thomas Munro wrote:
>
>> Thanks. As mentioned elsewhere in the thread, I discovered that the
>> same problem exists for page boundaries, with a different error
>> message. I've tried the attached repro scripts on 9.3.0, 9.3.5, 9.4.1
>> an
Bruce Momjian wrote:
> On Sun, Jun 14, 2015 at 11:21:35AM -0400, Tom Lane wrote:
> > For pretty much the same reason, I'm not in favor of small caps either.
> > Even assuming we can do that consistently (which I bet we can't; we
> > do not have all that much control over how web browsers render HT
Thomas Munro wrote:
> Thanks. As mentioned elsewhere in the thread, I discovered that the
> same problem exists for page boundaries, with a different error
> message. I've tried the attached repro scripts on 9.3.0, 9.3.5, 9.4.1
> and master with the same results:
>
> FATAL: could not access s
> Date: Thu, 4 Jun 2015 13:55:52 +0530
> From: Jeevan Chalke
> To: david.g.johns...@gmail.com
> Cc: PostgreSQL Hackers
> Subject: Re: [PATCH] two-arg current_setting() with fallback
> Message-ID:
>
> Hi,
>
> Attached patch which fixes my review comments.
>
> Since code changes were good, jus
Alvaro Herrera wrote:
> I see another hole in this area. See do_start_worker() -- there we only
> consider the offsets limit to determine a database to be in
> almost-wrapped-around state (causing emergency attention). If the
> database in members trouble has no pgstat entry, it might get comple
Hi Brendan,
Once the documentation/patch is ready can you pls share? I want to create an
alarm off a periodic query on the queue size for say 4GB/some count that I
tune.
Thanks,
Kevin
--
View this message in context:
http://postgresql.nabble.com/Function-to-get-size-of-notification-queue-tp
Hi all,
I noticed while using gin function of pageinspect that there are some
inconsistency data types.
For example, data type of GinMetaPageData.head, and tail is
BlockNumber, i.g, uint32.
But in ginfunc.c, we get that value as int64.
So I think the output is odd a little. Is it intentional?
-
On Sun, Jun 14, 2015 at 02:12:16PM -0400, Bruce Momjian wrote:
> I have run a script to count the number of "" items in the
> major release notes of each major version of Postgres back to 7.4:
>
> 7.4280
> 8.0238
> 8.1187
> 8.2230
> 8.3237
>
On Sun, Jun 14, 2015 at 11:21:35AM -0400, Tom Lane wrote:
> Bruce Momjian writes:
> > OK, new idea. What about, instead of having the last name be all-caps,
> > we have the last name start with an uppercase letter, then use smallcaps
> > for the rest of the last name:
> > https://en.wikipedia
On Mon, Jun 15, 2015 at 08:47:12AM -0400, Tom Lane wrote:
> Noah Misch writes:
> > While Windows was the bellwether, harm potential is greater on non-Windows
> > systems. pg_perm_setlocale() sets the LC_CTYPE environment variable to help
> > PL/Perl avoid clobbering the process locale; see plperl
Hello,
>Maybe, For DBAs,
>It might be better to show vacuum progress in pg_stat_activity.
>(if we'd do, add a free-style column like "progress" ?) This column might also
>be able to use for other long time commands like ANALYZE, CREATE/RE INDEX and
>COPY. To realize this feature, we certainly ne
17 matches
Mail list logo
