On Wed, Aug 31, 2016 at 11:56 AM, Pavel Stehule wrote:
> It is pity - lot of performance issues are related to this missing feature.
I don't think you are being very clear about what feature you are
talking about. The feature that Jeevan has implemented is pushing
aggregates to the remote side w
On 2016/08/29 20:53, Robert Haas wrote:
> On Fri, Aug 26, 2016 at 1:33 PM, Amit Langote
> wrote:
>> We do take a lock on the parent because we would be changing its partition
>> descriptor (relcache). I changed MergeAttributes() such that an
>> AccessExclusiveLock instead of ShareUpdateExclusiveL
On Mon, Aug 29, 2016 at 6:04 AM, Kouhei Kaigai wrote:
> I noticed the source code comment around CustomPath structure says "see above"
> for definition of CUSTOMPATH_* flags. It was originally right, but it was
> moved
> to nodes/extensible.h on the further development. So, no comments are above.
On Wed, Aug 31, 2016 at 12:37 PM, Amit Langote
wrote:
>>> If we need an AccessExclusiveLock on parent to add/remove a partition
>>> (IOW, changing that child table's partitioning information), then do we
>>> need to lock the individual partitions when reading partition's
>>> information? I mean t
On Wed, Aug 31, 2016 at 7:47 AM, Tom Lane wrote:
> Michael Paquier writes:
>> [ malloc-nulls-v5.patch ]
>
> I've committed some form of all of these changes
Thanks!
> except the one in
> adt/pg_locale.c. I'm not entirely sure whether we need to do anything
> about that at all, but if we do, th
On 2016/08/31 16:17, Robert Haas wrote:
> On Wed, Aug 31, 2016 at 12:37 PM, Amit Langote wrote:
>> What I was trying to understand is why this would not be possible
>> with a design where partition bound is stored in the catalog as a property
>> of individual partitions instead of a design where we
2016-08-31 9:00 GMT+02:00 Robert Haas :
> On Wed, Aug 31, 2016 at 11:56 AM, Pavel Stehule
> wrote:
> > It is pity - lot of performance issues are related to this missing
> feature.
>
> I don't think you are being very clear about what feature you are
> talking about. The feature that Jeevan has
Hi all,
Cleanup $subject has been raised a couple of times, like one year ago here:
https://www.postgresql.org/message-id/cab7npqrxvq+q66ufzd9wa5uaftyn4wauadbjxkfrync96kf...@mail.gmail.com
And more recently here while working on the NULL checks for malloc():
https://www.postgresql.org/message-id/C
On 2016/08/31 16:42, Pavel Stehule wrote:
> 2016-08-31 9:00 GMT+02:00 Robert Haas :
>
>> On Wed, Aug 31, 2016 at 11:56 AM, Pavel Stehule
>> wrote:
>>> It is pity - lot of performance issues are related to this missing
>> feature.
>>
>> I don't think you are being very clear about what feature you
Hi Aleksander,
This has already been fixed with commit
4f9f495889d3d410195c9891b58228727b340189
Thanks
On Fri, Apr 8, 2016 at 6:02 PM, Aleksander Alekseev <
a.aleks...@postgrespro.ru> wrote:
> Hello
>
> Currently there is a following piece of code in snapmgr.c:
>
> ```
> /* Copy all required fi
Hi,
attached is a small patch that adds an -N option to pg_restore, in order
to exclude a schema, in addition to -n for the restriction to a schema.
In principle, this could be extended to -t etc., but I think having this
for schemas would be the most useful with the least effort.
One use case f
On Fri, 26 Aug 2016 10:10:33 +0530
Mithun Cy wrote:
> On Thu, Mar 17, 2016 at 4:47 AM, David Steele
> wrote:
> >Since there has been no response from the author I have marked this
> >patch
> "returned with feedback". Please feel free >to resubmit for 9.7!
> I have started to work on this patc
On Tue, 30 Aug 2016 14:54:57 +0530
Mithun Cy wrote:
> On Fri, Aug 26, 2016 at 10:10 AM, Mithun Cy
> wrote:
> >
> > >rpath,'/home/mithun/edbsrc/patch6bin/lib',--enable-new-dtags
> > >-lecpg
> > -lpgtypes -lpq -lpgcommon -lpgport -lz -lrt -lcrypt -ldl -lm -o
> > test1
> > >../../../../../s
2016-08-31 10:03 GMT+02:00 Amit Langote :
> On 2016/08/31 16:42, Pavel Stehule wrote:
> > 2016-08-31 9:00 GMT+02:00 Robert Haas :
> >
> >> On Wed, Aug 31, 2016 at 11:56 AM, Pavel Stehule <
> pavel.steh...@gmail.com>
> >> wrote:
> >>> It is pity - lot of performance issues are related to this missi
Hi Tom,
On Tue, 2016-08-30 at 08:18 -0400, Tom Lane wrote:
> The above isn't ever likely to work for any large value of "work",
> because the function would be confused about what the table rowtype
> is. I thought we had adequate defenses in there to throw an error
> if you try to access a table
> On 31 Aug 2016, at 03:28, Craig Ringer wrote:
>
> On 25 Aug. 2016 20:03, "Stas Kelvich" wrote:
> >
> > Thanks for clarification about how restart_lsn is working.
> >
> > Digging slightly deeper into this topic revealed that problem was in two
> > phase decoding, not it logical decoding itself
> Hi Aleksander,
>
> This has already been fixed with commit
> 4f9f495889d3d410195c9891b58228727b340189
>
> Thanks
Agree, it's fixed now. Thank you!
--
Best regards,
Aleksander Alekseev
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscriptio
On 2016/08/01 21:14, Etsuro Fujita wrote:
I noticed that the following note about direct modification via
GetForeignUpperPaths in fdwhandler.sgml is a bit confusing. We have
another approach using PlanDirectModify, so that should be reflected in
the note as well. Please find attached a patch.
On Wed, Aug 31, 2016 at 12:10 AM, Tom Lane wrote:
> Fujii Masao writes:
>> I found that pg_xlogdump code for XLOG_GIN_INSERT record with
>> GIN_INSERT_ISLEAF flag has the same issue, i.e.,
>> "unknown action 0" error is thrown for that record.
>> The latest patch fixes this.
>
> Hmm, comparing gi
Hi,
Now that we are OK with static inline functions, we can save some cycles
from floating-point functions, by turning Float4GetDatum,
Float8GetDatum, and DatumGetFloat8 into static inlines. They are only a
few instructions, but couldn't be implemented as macros before, because
they need a lo
Em quarta-feira, 31 de agosto de 2016, Michael Banck
escreveu:
> Hi,
>
> attached is a small patch that adds an -N option to pg_restore, in order
> to exclude a schema, in addition to -n for the restriction to a schema.
>
> In principle, this could be extended to -t etc., but I think having this
Robert Haas writes:
> On Tue, Aug 30, 2016 at 6:38 PM, Tom Lane wrote:
>> Robert, could you fix the documentation for that field so it's
>> intelligible?
> Uh, maybe. The trick, as you've already noted, is finding something
> better. Maybe this:
> -boolsingle_copy;/* path must
Fujii Masao writes:
> On Wed, Aug 31, 2016 at 12:10 AM, Tom Lane wrote:
>> Hmm, comparing gin_desc() to ginRedoInsert() makes me think there are more
>> problems there than that one. Aren't the references to "payload" wrong
>> in all three branches of that "if" construct, not just the middle one
Heikki Linnakangas writes:
> Now that we are OK with static inline functions, we can save some cycles
> from floating-point functions, by turning Float4GetDatum,
> Float8GetDatum, and DatumGetFloat8 into static inlines.
Looks good to me.
I wonder whether there is a compiler-dependent way of av
On 08/31/2016 02:38 PM, Tom Lane wrote:
Heikki Linnakangas writes:
Now that we are OK with static inline functions, we can save some cycles
from floating-point functions, by turning Float4GetDatum,
Float8GetDatum, and DatumGetFloat8 into static inlines.
Looks good to me.
Ok, will push.
I
When SSL renegotiation was removed in 426746b9 the only consumer of the openssl
specific count member in the Port struct was removed, but the member was left
together with a few updates to it which are unused. Attached patch removes the
leftovers which now serves no purpose unless I’m missing some
Michael Paquier writes:
> On Tue, Aug 30, 2016 at 11:00 PM, Tom Lane wrote:
>> Thinking about it some more ... what we actually need to prevent, AFAICS,
>> is standby_mode becoming true in a standalone backend.
> I have spent some time playing with that and you are right. Only
> standby_mode = o
On 2016-08-30 11:22:43 +0300, Maksim Milyutin wrote:
Hi,
On 2016-08-29 18:22:56 +0300, maksim wrote:
Now I complete extension that provides facility to see the current state of
query execution working on external session in form of EXPLAIN ANALYZE
output. This extension works on 9.5 version,
On Wed, Aug 31, 2016 at 6:41 AM, Jaime Casanova
wrote:
>
> On 30 August 2016 at 23:10, Joel Jacobson wrote:
> >
> > There should be a way to within the session and/or txn permanently
> > block autonomous transactions.
> >
>
> This will defeat one of the use cases of autonomous transactions: audit
Daniel Gustafsson writes:
> When SSL renegotiation was removed in 426746b9 the only consumer of the
> openssl
> specific count member in the Port struct was removed, but the member was left
> together with a few updates to it which are unused. Attached patch removes
> the
> leftovers which now
Hi,
Am Mittwoch, den 31.08.2016, 07:59 -0300 schrieb Fabrízio de Royes
Mello:
> Please add it to the next open commitfest.
I had done so already: https://commitfest.postgresql.org/10/762/
Regards,
Michael
--
Michael Banck
Projektleiter / Senior Berater
Tel.: +49 2166 9901-171
Fax: +49 2166
While I was hacking around sequence stuff, I felt the urge to look into
an old peeve: That sequence metadata is not stored in a proper catalog.
Right now in order to find out some metadata about sequences (min, max,
increment, etc.), you need to look into the sequence. That is like
having to query
On 29 August 2016 at 12:34, Tom Lane wrote:
> Simon Riggs writes:
>> Fix pg_receivexlog --synchronous
>
> The buildfarm says you broke the 9.5 branch.
>
> In general, pushing inessential patches just a few hours before a wrap
> deadline is a dangerous business. Pushing them without any testing
>
2016-08-31 15:09 GMT+02:00 Joel Jacobson :
> On Wed, Aug 31, 2016 at 6:41 AM, Jaime Casanova
> wrote:
> >
> > On 30 August 2016 at 23:10, Joel Jacobson wrote:
> > >
> > > There should be a way to within the session and/or txn permanently
> > > block autonomous transactions.
> > >
> >
> > This wi
On 27 August 2016 at 12:09, Kuntal Ghosh wrote:
>>> * wal_consistency_mask = 511 /* Enable consistency check mask bit*/
>>
>> What does this mean? (No docs)
>
> I was using this parameter as a masking integer to indicate the
> operations(rmgr list) for which we need this feature to be enabled.
>
On 8/30/16 10:12 AM, Pavel Stehule wrote:
I am working on pgaudit customization for one my customer.
There are few requests:
1. flat format without complex types, without nesting - CSV is ideal.
2. all important attributes should be separated - is not possible to
search in original queries: ta
On 31 August 2016 at 21:17, Peter Eisentraut
wrote:
> While I was hacking around sequence stuff, I felt the urge to look into
> an old peeve: That sequence metadata is not stored in a proper catalog.
> Right now in order to find out some metadata about sequences (min, max,
> increment, etc.), you
Heikki Linnakangas writes:
> On 08/31/2016 02:38 PM, Tom Lane wrote:
>> I wonder whether there is a compiler-dependent way of avoiding the union
>> trick ... or maybe gcc is already smart enough that it doesn't matter?
> It seems to compile into a single instruction, so it can't get any
> better
On Wed, Aug 31, 2016 at 2:50 AM, Peter Eisentraut
wrote:
> - A API interface to open a "connection" to a background worker, run
> queries, get results: AutonomousSessionStart(), AutonomousSessionEnd(),
> AutonomousSessionExecute(), etc. The communication happens using the
> client/server protocol
On 8/31/16 9:39 AM, David Steele wrote:
On 8/30/16 10:12 AM, Pavel Stehule wrote:
#3 is not likely without changes to logging in Postgres. However, there
are plenty of tools for log analysis (e.g. ELK) that might help and a
Postgres extension that allows log messages to be directed elsewhere
Craig Ringer writes:
> On 31 August 2016 at 21:17, Peter Eisentraut
> wrote:
>> I don't know if this is a net improvement. Maybe this introduces as
>> many new issues as it removes. But I figured I'll post this, so that at
>> least we can discuss it.
> This will change behaviour subtly.
Uh, n
> On 31 Aug 2016, at 15:12, Tom Lane wrote:
>
> Daniel Gustafsson writes:
>> When SSL renegotiation was removed in 426746b9 the only consumer of the
>> openssl
>> specific count member in the Port struct was removed, but the member was left
>> together with a few updates to it which are unused
I wrote:
> Personally, my big beef with the current approach to sequences is that
> we eat a whole relation (including a whole relfilenode) per sequence.
> I wish that we could reduce a sequence to just a single row in a
> catalog, including the nontransactional state. Not sure how feasible
> that
On 31 August 2016 at 21:46, Greg Stark wrote:
> On Wed, Aug 31, 2016 at 2:50 AM, Peter Eisentraut
> wrote:
>> - A API interface to open a "connection" to a background worker, run
>> queries, get results: AutonomousSessionStart(), AutonomousSessionEnd(),
>> AutonomousSessionExecute(), etc. The co
Hello hello,
Here's a rebased and updated patch for $SUBJECT for the September commit
fest.
.m
*** a/doc/src/sgml/ref/insert.sgml
--- b/doc/src/sgml/ref/insert.sgml
***
*** 22,33 PostgreSQL documentation
[ WITH [ RECURSIVE ] with_query [, ...] ]
! INSERT INTO table_n
Hi hackers,
Few days earlier I've finished my work on WAITLSN statement utility, so
I’d like to share it.
Introduction
Our clients who deal with 9.5 and use asynchronous master-slave
replication, asked to make the wait-mechanism on the slave side to
prevent the situation when
On 31 August 2016 at 22:01, Tom Lane wrote:
> Personally, my big beef with the current approach to sequences is that
> we eat a whole relation (including a whole relfilenode) per sequence.
> I wish that we could reduce a sequence to just a single row in a
> catalog, including the nontransactional
On 31/08/16 16:10, Tom Lane wrote:
I wrote:
Personally, my big beef with the current approach to sequences is that
we eat a whole relation (including a whole relfilenode) per sequence.
I wish that we could reduce a sequence to just a single row in a
catalog, including the nontransactional state.
2016-08-31 16:00 GMT+02:00 David Steele :
> On 8/31/16 9:39 AM, David Steele wrote:
>
>> On 8/30/16 10:12 AM, Pavel Stehule wrote:
>>
>
> #3 is not likely without changes to logging in Postgres. However, there
>> are plenty of tools for log analysis (e.g. ELK) that might help and a
>> Postgres ex
I've been profiling simple aggregate queries, looking for any
low-hanging fruit. For this query:
-- setup
create table floats as select g::float8 as a, g::float8 as b, g::float8
as c from generate_series(1, 1000) g;
vacuum freeze floats;
-- query
select sum(a), sum(b+c) from floats;
pe
On 31/08/16 16:11, Craig Ringer wrote:
On 31 August 2016 at 21:46, Greg Stark wrote:
On Wed, Aug 31, 2016 at 2:50 AM, Peter Eisentraut
wrote:
- A API interface to open a "connection" to a background worker, run
queries, get results: AutonomousSessionStart(), AutonomousSessionEnd(),
Autonomous
On 31 August 2016 at 22:16, Ivan Kartyshov wrote:
> Our clients who deal with 9.5 and use asynchronous master-slave replication,
> asked to make the wait-mechanism on the slave side to prevent the situation
> when slave handles query which needs data (LSN) that was received, flushed,
> but still
Hi hackers,
Recently I have finished my work on a patch for pg_buffercache contrib,
I think it's time to share my results.
Introduction
I want to offer you the implementation that allows to decrease system
workload by
partially sacrificing (fully snapshot consistency) data cons
[trimmed cc list because of big attachments]
On 8/16/16 4:22 PM, Jim Nasby wrote:
> Joy, do you have an idea what a *minimally invasive* patch for C++
> support would look like? That's certainly the first step here.
I developed a minimally invasive patch for C++ support a few years ago
shortly a
Michael Paquier writes:
> Which means that processes have an escape window when initializing
> shared memory by cleaning up the index if an entry cannot be found and
> then cannot be created properly. I don't think that it is a good idea
> to change that by forcing ShmemAlloc to fail. So I would t
Craig Ringer writes:
> On 31 August 2016 at 22:01, Tom Lane wrote:
>> Personally, my big beef with the current approach to sequences is that
>> we eat a whole relation (including a whole relfilenode) per sequence.
>> I wish that we could reduce a sequence to just a single row in a
>> catalog, inc
Hi
I propose a new type of psql variables - file references. The content of
file reference is specified by referenced file. It allows simple inserting
large data without necessity of manual escaping or using LO api.
When I wrote the patch, I used parametrized queries for these data instead
escape
On 2016-08-31 11:23:27 -0400, Tom Lane wrote:
> Another issue is what is the low-level interlock between nextvals
> in different processes. Right now it's the buffer lock on the
> sequence's page. With a scheme like this, if we just kept doing
> that, we'd have a single lock covering probably O(1
Hi,
On 2016-08-31 17:47:18 +0300, Heikki Linnakangas wrote:
> # .. .
>
> #
> 25.70% 0.00% postmaster [unknown] [k]
> 14.23%13.75% postmaster postgres [.] Ex
Andres Freund wrote:
> On 2016-08-31 11:23:27 -0400, Tom Lane wrote:
> > Another issue is what is the low-level interlock between nextvals
> > in different processes. Right now it's the buffer lock on the
> > sequence's page. With a scheme like this, if we just kept doing
> > that, we'd have a si
On 08/31/2016 06:51 PM, Andres Freund wrote:
On 2016-08-31 17:47:18 +0300, Heikki Linnakangas wrote:
We actually used to call ExecEvalExpr() directly for each argument, but that
was changed by the patch that added support for ordered set aggregates. It
looks like that was a bad idea, from a perf
On 2016-08-31 19:07:00 +0300, Heikki Linnakangas wrote:
> On 08/31/2016 06:51 PM, Andres Freund wrote:
> > I've first combined the projection for all the aggregates, ordered set,
> > or not, into one projetion. That got rid of a fair amount of overhead
> > when you have multiple aggregates. I atta
This is a summary of proposed changes to the recovery.conf API for
v10. These are based in part on earlier discussions, and represent a
minimal modification to current usage.
Proposed changes (with reference to patches from Abhijit Menon-Sen and myself)
* pg_ctl start -M (normal|recover|continue)
On 2016-08-31 12:56:45 -0300, Alvaro Herrera wrote:
> I was thinking that nextval could grab a shared buffer lock and release
> immediately, just to ensure no one holds exclusive buffer lock
> concurrently (which would be used for things like dropping one seq tuple
> from the page, when a sequence
On Wed, Aug 31, 2016 at 11:32 AM, Pavel Stehule
wrote:
> Hi
>
> I propose a new type of psql variables - file references. The content of
> file reference is specified by referenced file. It allows simple inserting
> large data without necessity of manual escaping or using LO api.
>
> When I wrote
On 31 August 2016 at 14:09, Joel Jacobson wrote:
> On Wed, Aug 31, 2016 at 6:41 AM, Jaime Casanova
> wrote:
>>
>> On 30 August 2016 at 23:10, Joel Jacobson wrote:
>> >
>> > There should be a way to within the session and/or txn permanently
>> > block autonomous transactions.
>> >
>>
>> This will
2016-08-31 18:24 GMT+02:00 Corey Huinker :
> On Wed, Aug 31, 2016 at 11:32 AM, Pavel Stehule
> wrote:
>
>> Hi
>>
>> I propose a new type of psql variables - file references. The content of
>> file reference is specified by referenced file. It allows simple inserting
>> large data without necessit
Andres Freund writes:
> On 2016-08-31 12:56:45 -0300, Alvaro Herrera wrote:
>> I was thinking that nextval could grab a shared buffer lock and release
>> immediately, just to ensure no one holds exclusive buffer lock
>> concurrently (which would be used for things like dropping one seq tuple
>> fr
On Wed, Aug 31, 2016 at 3:11 PM, Craig Ringer wrote:
>
> I suspect that there'll be way too much code that relies on stashing
> xact-scoped stuff in globals for that to be viable. Caches alone.
> Peter will be able to explain more, I'm sure.
>
> We'd probably need a new transaction data object tha
On Wed, Aug 31, 2016 at 1:45 PM, Pavan Deolasee
wrote:
> We discussed a few ideas to address the "Duplicate Scan" problem. For
> example, we can teach Index AMs to discard any duplicate (key, CTID) insert
> requests. Or we could guarantee uniqueness by either only allowing updates
> in one lexica
Hi,
On 2016-08-31 12:53:30 -0400, Tom Lane wrote:
> Improving on the space wastage is exactly the point IMO. If it's still
> going to be 8k per sequence on disk (*and* in shared buffers, remember),
> I'm not sure it's worth all the work to change things at all.
A separate file is a heck lot more
Andres Freund wrote:
> Hi,
>
> On 2016-08-31 12:53:30 -0400, Tom Lane wrote:
> > Improving on the space wastage is exactly the point IMO. If it's still
> > going to be 8k per sequence on disk (*and* in shared buffers, remember),
> > I'm not sure it's worth all the work to change things at all.
>
On 2016-08-31 14:25:43 -0300, Alvaro Herrera wrote:
> Andres Freund wrote:
> > Hi,
> >
> > On 2016-08-31 12:53:30 -0400, Tom Lane wrote:
> > > Improving on the space wastage is exactly the point IMO. If it's still
> > > going to be 8k per sequence on disk (*and* in shared buffers, remember),
> >
Heikki Linnakangas writes:
> Use static inline functions for float <-> Datum conversions.
Hmm, it looks like narwhal for one is not happy with this:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=narwhal&dt=2016-08-31%2016%3A00%3A03
I suspect the failure traces to this bit in pg_enum.c:
On Tue, Aug 30, 2016 at 7:46 PM, Peter Eisentraut
wrote:
> Here is a patch I've been working on to allow the use of ICU for sorting
> and other locale things.
I'm really happy that you're working on this. This is more important
than is widely appreciated, and very important overall.
In a world w
On 08/31/2016 08:27 PM, Tom Lane wrote:
Heikki Linnakangas writes:
Use static inline functions for float <-> Datum conversions.
Hmm, it looks like narwhal for one is not happy with this:
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=narwhal&dt=2016-08-31%2016%3A00%3A03
I suspect the
On Tue, Aug 30, 2016 at 7:46 PM, Peter Eisentraut
wrote:
> In initdb, I initialize the default collation set as before from the
> `locale -a` output, but also add all available ICU locales with a "%icu"
> appended (so "fr_FR%icu"). I suppose one could create a configuration
> option perhaps in in
Heikki Linnakangas writes:
> On 08/31/2016 08:27 PM, Tom Lane wrote:
>> We had a bunch of similar problems in the recent work on exact degree trig
>> functions, and eventually found that storing values into volatile float8
>> variables was the most reliable way to force rounding to the expected
>>
and...@anarazel.de (Andres Freund) writes:
> On 2016-08-31 14:25:43 -0300, Alvaro Herrera wrote:
>> Yes, sure, we're still improving even if we stick to one-seq-per-bufpage,
>> but while we're at it, we could as well find a way to make it as best as
>> we can. And allowing multiple seqs per page s
On 2016-08-31 13:59:48 -0400, Tom Lane wrote:
> and...@anarazel.de (Andres Freund) writes:
> > On 2016-08-31 14:25:43 -0300, Alvaro Herrera wrote:
> >> Yes, sure, we're still improving even if we stick to one-seq-per-bufpage,
> >> but while we're at it, we could as well find a way to make it as bes
On Wed, Aug 31, 2016 at 10:38 PM, Claudio Freire
wrote:
>
> On Wed, Aug 31, 2016 at 1:45 PM, Pavan Deolasee
> wrote:
>
>> We discussed a few ideas to address the "Duplicate Scan" problem. For
>> example, we can teach Index AMs to discard any duplicate (key, CTID) insert
>> requests. Or we could
On Wed, Aug 24, 2016 at 12:39 PM, Andres Freund wrote:
>
>
> On August 24, 2016 9:32:48 AM PDT, Tomas Vondra <
> tomas.von...@2ndquadrant.com> wrote:
> >
> >
> >On 08/24/2016 12:20 AM, Andres Freund wrote:
> >> On 2016-08-23 19:18:04 -0300, Claudio Freire wrote:
> >>> On Tue, Aug 23, 2016 at 7:11
Andres Freund writes:
> On 2016-08-31 13:59:48 -0400, Tom Lane wrote:
>> You are ignoring the performance costs associated with eating 100x more
>> shared buffer space than necessary.
> I doubt that's measurable in any real-world scenario. You seldomly have
> hundreds of thousands of sequences th
On 2016-08-31 14:23:41 -0400, Tom Lane wrote:
> Andres Freund writes:
> > On 2016-08-31 13:59:48 -0400, Tom Lane wrote:
> >> You are ignoring the performance costs associated with eating 100x more
> >> shared buffer space than necessary.
>
> > I doubt that's measurable in any real-world scenario.
> On Aug 31, 2016, at 6:46 AM, Greg Stark wrote:
>
> Using a background worker mean that the autonomous transaction can't
> access any state from the process memory. Parameters in plpgsql are a
> symptom of this but I suspect there will be others. What happens if a
> statement timeout occurs dur
At 2016-08-31 17:15:59 +0100, si...@2ndquadrant.com wrote:
>
> * Recovery parameters would now be part of the main postgresql.conf
> infrastructure
> Any parameters set in $DATADIR/recovery.conf will be read after the
> main parameter file, similar to the way that postgresql.conf.auto is
> read.
>
On 08/24/2016 06:16 PM, Robert Haas wrote:
> On Tue, Aug 23, 2016 at 6:11 PM, Tomas Vondra
> wrote:
>> Could someone please explain how the unlogged tables are supposed to fix the
>> catalog bloat problem, as stated in the initial patch submission? We'd still
>> need to insert/delete the catalog r
On Wed, Aug 31, 2016 at 10:15:33PM +0530, Pavan Deolasee wrote:
> Instead, what I would like to propose and the patch currently implements is to
> restrict WARM update to once per chain. So the first non-HOT update to a tuple
> or a HOT chain can be a WARM update. The chain can further be HOT updat
On Wed, Aug 31, 2016 at 04:03:29PM -0400, Bruce Momjian wrote:
> Why not just remember the tid of chains converted from WARM to HOT, then
> use "amrecheck" on an index entry matching that tid to see if the index
> matches one of the entries in the chain. (It will match all of them or
> none of the
Hi all. I’m new to the PostgreSQL code and the mailing list, but I’ve had a lot
of experience with using ICU in a different database product. So while I’m not
up to speed on the code yet, I can offer some insights on using ICU.
> On Aug 30, 2016, at 9:12 PM, Peter Eisentraut
> wrote:
>> How st
I have merged in the changes since v4 (a year and a half ago) and
cured all bit-rot I found, to get the attached v5 which runs `make
check world` without problem -- including the tests added for this
feature.
I did remove the contrib code that David Fetter wrote to
demonstrate the correctness and
On Thu, Aug 18, 2016 at 5:26 PM, Andres Freund wrote:
> Rebased version attached. A review would be welcome. Plan to push this
> forward otherwise in the not too far away future.
This looks good.
The only thing that stuck out to any degree is that we don't grow the
"reln->md_seg_fds[forknum]" ar
On Wed, Aug 31, 2016 at 2:09 PM, Peter Geoghegan wrote:
> The only thing that stuck out to any degree is that we don't grow the
> "reln->md_seg_fds[forknum]" array within the new _fdvec_resize()
> function geometrically.
That new function looks like this:
> +static void
> +_fdvec_resize(SMgrRela
Michael Paquier writes:
> Cleanup $subject has been raised a couple of times, like one year ago here:
> https://www.postgresql.org/message-id/cab7npqrxvq+q66ufzd9wa5uaftyn4wauadbjxkfrync96kf...@mail.gmail.com
> And more recently here while working on the NULL checks for malloc():
> https://www.pos
On Sun, Nov 22, 2015 at 7:29 PM, Andreas Karlsson wrote:
> Sorry for dropping this patch, but now I have started looking at it again.
Any chance of picking this up again soon, Andreas? I think it's an
important project. I would like to review it.
--
Peter Geoghegan
--
Sent via pgsql-hackers
On 2016-08-31 14:09:47 -0700, Peter Geoghegan wrote:
> On Thu, Aug 18, 2016 at 5:26 PM, Andres Freund wrote:
> > Rebased version attached. A review would be welcome. Plan to push this
> > forward otherwise in the not too far away future.
>
> This looks good.
Thanks for looking!
> The only thin
On 08/31/2016 09:20 PM, Vik Fearing wrote:
> On 08/24/2016 06:16 PM, Robert Haas wrote:
>> On Tue, Aug 23, 2016 at 6:11 PM, Tomas Vondra
>> wrote:
>>> Could someone please explain how the unlogged tables are supposed to fix the
>>> catalog bloat problem, as stated in the initial patch submission
On 2016-08-31 23:40:46 +0200, Tomas Vondra wrote:
> It's an improvement (and it's pretty much exactly what I proposed
> upthread). But it does not solve the problems with pg_statistic for
> example (each backend needs it's own statistics. So we'd either bloat
> the pg_statistic (if we manage to sol
Attached patch adds support for -X stream to work with .tar and .tar.gz
file formats.
If tar mode is specified, a separate pg_xlog.tar (or .tar.gz) file is
created and the data is streamed into it. Regular mode is (should not) see
any changes in how it works.
The implementation creates a "walmeth
On 08/31/2016 11:43 PM, Andres Freund wrote:
> On 2016-08-31 23:40:46 +0200, Tomas Vondra wrote:
>> It's an improvement (and it's pretty much exactly what I proposed
>> upthread). But it does not solve the problems with pg_statistic for
>> example (each backend needs it's own statistics. So we'd
1 - 100 of 130 matches
Mail list logo
