Haribabu kommi haribabu.ko...@huawei.com writes:
To handle the above case instead of directly resetting the dead tuples as
zero, how if the exact dead tuples
are removed from the table stats. With this approach vacuum gets triggered
frequently thus it reduces the bloat.
This does not seem
This paragraph reads a bit strange to me:
+ A statistics session is the time period when statistics are gathered by
statistics collector
+ without being reset. So a statistics session continues across normal
shutdowns,
+ but whenever statistics are reset, like during a crash or upgrade,
I think it is desirable that this patch should be resubmitted for the next
CommitFest for further review and testing mentioned above. So I'd like to mark
this patch as Returned with Feedback. Is it OK?
Sounds like a good idea. Thanks for the review!
Ian Link
Etsuro Fujita
On Oct 12, 2013 2:13 AM, MauMau maumau...@gmail.com wrote:
From: Bruce Momjian br...@momjian.us
On Thu, Oct 10, 2013 at 11:01:52PM +0900, MauMau wrote:
Although this is not directly related to memory, could you set
max_prepared_transactions = max_connections at initdb time? People
must
On Oct 11, 2013 10:23 PM, Josh Berkus j...@agliodbs.com wrote:
On 10/11/2013 01:11 PM, Bruce Momjian wrote:
In summary, I think we need to:
* decide on new defaults for work_mem and maintenance_work_mem
* add an initdb flag to allow users/packagers to set shared_bufffers?
* add an
On Sat, Oct 12, 2013 at 1:55 AM, Tomas Vondra t...@fuzzy.cz wrote:
On 10.10.2013 13:57, Heikki Linnakangas wrote:
On 09.10.2013 02:04, Tomas Vondra wrote:
On 8.10.2013 21:59, Heikki Linnakangas wrote:
On 08.10.2013 17:47, Alexander Korotkov wrote:
Hi, Tomas!
On Sun, Oct 6, 2013 at
On Fri, Oct 11, 2013 at 10:36 PM, Andres Freund and...@2ndquadrant.com wrote:
On 2013-10-11 09:22:50 +0530, Amit Kapila wrote:
I think it will be difficult to prove by using any compression
algorithm, that it compresses in most of the scenario's.
In many cases it can so happen that the WAL
On 12.10.2013 12:11, Alexander Korotkov wrote:
On Sat, Oct 12, 2013 at 1:55 AM, Tomas Vondra t...@fuzzy.cz
mailto:t...@fuzzy.cz wrote:
Yup, this version fixed the issues. I haven't been able to do any
benchmarks yet, all I have is some basic stats
| HEAD |
I briefly checked these patches. Let me add some comments.
* terminate-worker-v1.patch
TerminateBackgroundWorker() turns on slot-terminate flag under
LW_SHARED lock. Is it reasonable because all the possible caller
is the background worker process itself, isn't it?
* ephemeral-precious-v1.patch
Hi,
As discussed in 20130926225545.gb26...@awork2.anarazel.de and on quite
some other occasions there's quite some scalability improvements we
could make if we had cross platform support for atomic
operations. Providing that is a fair bit of work for every
architecture/compiler/OS, so I think
On 11.10.2013 13:42, Huchev wrote:
gettimeofday(start, NULL);
for (i = 0; i VALUES; i++) {
state = XXH32_init(result);
XXH32_update(state, i, 4);
XXH32_digest(state);
}
gettimeofday(end, NULL);
This code is using the update variant, which is only
On Sat, Oct 12, 2013 at 5:46 PM, Andres Freund and...@2ndquadrant.com wrote:
I think we should remove support the following ports:
- IRIX
- UnixWare
- Tru64
Neither of those are relevant.
Seems reasonable.
I think we should remove support for the following architectures:
- VAX
Agreed.
12 matches
Mail list logo
