On Tue, Dec 26, 2017 at 10:47:59PM -0800, Robert Haas wrote:
> On Tue, Dec 26, 2017 at 4:14 AM, Michael Paquier
> wrote:
>> On Tue, Dec 26, 2017 at 4:30 PM, Andres Freund wrote:
>>> You're proposing to lock the entire relation against many forms of
>>> concurrent DDL, just to get rid of that err
Bonjour Michaël,
And my 2c on the matter is that switching silently from one version to
the other would be unwelcome. The user should be aware if a test is
overflowing a number when specifying an integer.
This whole integer pow version is becoming unduly complicated and ugly.
For me, the rat
On 23 December 2017 at 11:58, Michael Paquier wrote:
> On Fri, Dec 22, 2017 at 07:55:19AM +0100, Feike Steenbergen wrote:
>> On 21 December 2017 at 05:32, Michael Paquier
>> wrote:
>>
>> > Don't you want to put that in its own block? That's rather
>> > important not to miss for administrators.
On 22 December 2017 at 23:19, Maksim Milyutin wrote:
> On 22.12.2017 16:56, Craig Ringer wrote:
>
> On 22 December 2017 at 20:50, Maksim Milyutin
> wrote:
>
>> On 19.12.2017 16:54, Pavel Stehule wrote:
>>
>> sorry for small offtopic. Can be used this mechanism for log of executed
>> plan or full
On 25 December 2017 at 15:59, Konstantin Knizhnik wrote:
>
>
> On 25.12.2017 06:26, Craig Ringer wrote:
>
> On 24 December 2017 at 04:53, konstantin knizhnik <
> k.knizh...@postgrespro.ru> wrote:
>
>>
>>
>> But what if I just forbid to change recent_global_xmin?
>> If it is stalled at FirstNormal
On Tue, Dec 26, 2017 at 4:14 AM, Michael Paquier
wrote:
> On Tue, Dec 26, 2017 at 4:30 PM, Andres Freund wrote:
>> You're proposing to lock the entire relation against many forms of
>> concurrent DDL, just to get rid of that error? That seems unacceptable.
>> Isn't the canonical way to solve thi
On Sun, Dec 24, 2017 at 8:37 PM, Amit Kapila wrote:
> On Sun, Dec 24, 2017 at 12:06 PM, Robert Haas wrote:
>> On Fri, Dec 22, 2017 at 6:18 AM, Amit Kapila wrote:
>>
>>> Also, don't we need to use parallel_divisor for partial paths instead
>>> of non-partial paths as those will be actually distri
On Tue, Dec 26, 2017 at 7:51 PM, Michael Paquier
wrote:
>> > Hmm. What about the case where we try to open a plain file that's on
>> > an inaccessible filesystem, e.g. due to a disk failure? Allowing
>> > cancel to work just for FIFOs would be OK, I guess, but allowing it
>> > for other open() c
On Tue, Dec 26, 2017 at 02:00:47PM -0500, Peter Eisentraut wrote:
> On 12/25/17 00:32, Michael Paquier wrote:
> >> So here is a minimal patch set to perhaps wrap this up for the time
> >> being. I have added static assertions that check the sizes of
> >> GinNullCategory and GinTernaryValue, which
On Wed, Dec 27, 2017 at 10:18:03AM +0800, Adam Lee wrote:
> On Tue, Dec 26, 2017 at 11:48:58AM -0800, Robert Haas wrote:
> > On Thu, Dec 21, 2017 at 10:10 PM, Adam Lee wrote:
> > > I have an issue that COPY from a FIFO, which has no writers, could not be
> > > canceled, because COPY invokes Alloca
On Wed, Dec 27, 2017 at 12:58:28PM +1100, Vaishnavi Prabakaran wrote:
> I have added support in Postgres TAP test framework to backup a data
> directory with tablespace mapping. Also added support to move the backup
> directory contents to standby node, because current option to init the
> standby
On Tue, Dec 26, 2017 at 03:43:36PM -0700, legrand legrand wrote:
> would actual syntax
>
> WITH old_foo AS
> (select * from foo as of '')
> select * from foo except select * from old_foo;
>
> work in replacement for
>
> select * from foo except select * from foo as old_foo as of '';
>
> ?
If t
Hi,
Please find attached my 4th version this patch.
This is now based on v17 of Amit's faster partition pruning patch [1].
It also now includes Beena's tests which I've done some mostly
cosmetic changes to.
I've also fixed a few bugs, one in a case where I was not properly
handling zero matching
On Tue, Dec 26, 2017 at 11:48:58AM -0800, Robert Haas wrote:
> On Thu, Dec 21, 2017 at 10:10 PM, Adam Lee wrote:
> > I have an issue that COPY from a FIFO, which has no writers, could not be
> > canceled, because COPY invokes AllocateFile() -> fopen() -> blocking open().
>
> Hmm. What about the
Hi All,
I have added support in Postgres TAP test framework to backup a data
directory with tablespace mapping. Also added support to move the backup
directory contents to standby node, because current option to init the
standby from backup does not support copying softlinks, which is needed
when
On Tue, Dec 26, 2017 at 02:15:18PM -0500, Peter Eisentraut wrote:
> On 12/20/17 22:01, Stephen Frost wrote:
> > There's some downsides to this approach though: we do an initial set of
> > checks in ExecGrantStmt, but we can't do all of them because we don't
> > know if it's a sequence or not, so we
On Tue, Dec 26, 2017 at 11:26:58PM +0100, Fabien COELHO wrote:
> > This version looks good to me, except that I wonder if we should try to
> > switch to the floating-point version if the integer version would/does
> > overflow.
>
> My 0.02€ is that it is under the user control who provides either
Hi,
I've implemented the overflow checks and made some benchmarks and the
ipow() version became slower except with some specific inputs (base 0 for
example). It's true that the new auxiliary functions could be optimized,
but I don't think it makes sense to keep working on them just to match
pow()
On Tue, Dec 26, 2017 at 03:28:09PM -0500, Peter Eisentraut wrote:
> On 12/22/17 03:10, Michael Paquier wrote:
> > Second thoughts on 0002 as there is actually no need to move around
> > errorMessage if the PGconn* pointer is saved in the SCRAM status data
> > as both are linked. The attached simpli
would actual syntax
WITH old_foo AS
(select * from foo as of '')
select * from foo except select * from old_foo;
work in replacement for
select * from foo except select * from foo as old_foo as of '';
?
Regards
PAscal
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f19287
Hello Robert,
If a double is always returned, I'm wondering whether keeping the ipow
version makes much sense: In case of double loss of precision, the precision
is lost, too bad, and casting back to int won't bring it back.
I've kept it because knowing that both are ints enables not making a
On Thu, Dec 21, 2017 at 6:00 AM, Konstantin Knizhnik <
k.knizh...@postgrespro.ru> wrote:
> There is still one significant difference of my prototype implementation
> with SQL standard: it associates timestamp with select statement, not with
> particular table.
> It seems to be more difficult to s
This patch looks reasonable to me. I have also seen occasional requests
for this in the field.
If someone could test this on Windows, I think we could move ahead with it.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Se
On 12/22/17 03:10, Michael Paquier wrote:
> On Fri, Dec 22, 2017 at 11:59 AM, Michael Paquier
> wrote:
>> I have looked at how things could be done in symmetry for both the frontend
>> and backend code, and I have produced the attached patch 0002, which
>> can be applied on top of 0001 implementin
On Thu, Dec 21, 2017 at 10:10 PM, Adam Lee wrote:
> I have an issue that COPY from a FIFO, which has no writers, could not be
> canceled, because COPY invokes AllocateFile() -> fopen() -> blocking open().
Hmm. What about the case where we try to open a plain file that's on
an inaccessible filesy
On Fri, Dec 22, 2017 at 12:46 AM, Raúl Marín Rodríguez
wrote:
>> If a double is always returned, I'm wondering whether keeping the ipow
>> version makes much sense: In case of double loss of precision, the precision
>> is lost, too bad, and casting back to int won't bring it back.
>
> I've kept it
On 12/20/17 22:01, Stephen Frost wrote:
> There's some downsides to this approach though: we do an initial set of
> checks in ExecGrantStmt, but we can't do all of them because we don't
> know if it's a sequence or not, so we end up with some additional
> special checks to see if the GRANT is valid
On 12/25/17 00:32, Michael Paquier wrote:
>> So here is a minimal patch set to perhaps wrap this up for the time
>> being. I have added static assertions that check the sizes of
>> GinNullCategory and GinTernaryValue, which I think are the two critical
>> places that require compatibility with boo
Arthur Zakirov wrote:
> On Tue, Dec 26, 2017 at 01:55:57PM -0300, Alvaro Herrera wrote:
> > So what are you going to use instead?
>
> [ ... ]
>
> To allocate IspellDict in this case it is necessary to calculate needed
> memory size. I think arrays mentioned above will be built first then
> memcpy'
Thank you for your feedback.
On Tue, Dec 26, 2017 at 01:55:57PM -0300, Alvaro Herrera wrote:
> So what are you going to use instead?
For example, AffixNode and AffixNodeData represent prefix tree of an
affix list. They are accessed by Suffix and Prefix pointers of
IspellDict struct now. Instead a
2017-12-26 17:55 GMT+01:00 Alvaro Herrera :
> Arthur Zakirov wrote:
>
> > Implementation
> > --
> >
> > It is necessary to change all structures related with IspellDict:
> > SPNode, AffixNode, AFFIX, CMPDAffix, IspellDict itself. They all
> > shouldn't use pointers for this reason. Oth
Bonjour Daniel,
Most "permutation" functions are really cryptographic cyphers which are
quite expensive, and require powers of two, which is not what is needed.
ISTM that there are some constructs to deal with arbitrary sizes based on
cryptographic functions, but that would make it too expensiv
On Tue, Dec 26, 2017 at 8:31 AM, Alvaro Herrera
wrote:
> Jeff Janes wrote:
> > c3d09b3bd23f5f6 fixed it so concurrent CIC would not deadlock (or at
> least
> > not as reliably as before) by dropping its own snapshot before waiting
> for
> > all the other ones to go away.
> >
> > With commit 8aa3e
Arthur Zakirov wrote:
> Implementation
> --
>
> It is necessary to change all structures related with IspellDict:
> SPNode, AffixNode, AFFIX, CMPDAffix, IspellDict itself. They all
> shouldn't use pointers for this reason. Others are used only during
> dictionary building.
So what ar
Hello, hackers!
Introduction
I'm going to implement a patch which will store Ispell dictionaries in a shared
memory.
There is an extension shared_ispell [1], developed by Tomas Vondra. But it is a
bad candidate for including into contrib.
Because it should know a lot of informatio
Jeff Janes wrote:
> c3d09b3bd23f5f6 fixed it so concurrent CIC would not deadlock (or at least
> not as reliably as before) by dropping its own snapshot before waiting for
> all the other ones to go away.
>
> With commit 8aa3e47510b969354ea02a, concurrent CREATE INDEX CONCURRENTLY on
> different t
On 12/20/17 10:51, Tom Lane wrote:
> Peter Eisentraut writes:
>> On 12/20/17 00:57, Tom Lane wrote:
>>> I do not have a well-informed opinion on whether
>>> #if defined(__cpp_static_assert) && __cpp_static_assert >= 200410
>>> is an appropriate test for static_assert() being available, but I'm
>>>
> On 25 December 2017 at 18:40, Tomas Vondra
wrote:
> The attached v3 fixes this issue, and also a couple of other thinkos
Thank you for the patch, it looks quite interesting. After a quick look at
it
(mostly the first one so far, but I'm going to continue) I have a few
questions:
> + * XXX With
Yugo Nagata wrote:
> On Fri, 27 Oct 2017 07:11:14 +0200
> Robert Haas wrote:
>
> > On Wed, Oct 11, 2017 at 11:36 AM, Yugo Nagata wrote:
> > > In the attached patch, only automatically-updatable views that do not have
> > > INSTEAD OF rules or INSTEAD OF triggers are lockable. It is assumed that
Hi,
As of today, in the existing code in HeapTupleSatisfiesVacuum, if a
row is inserted via an aborted transaction, then it's deemed to be
dead immediately and can be cleaned up for re-use by HOT or vacuum,
etc.
With logical decoding, there might arise a case that such a row, if it
belongs to a s
2017-12-26 14:46 GMT+01:00 Lelisa Diriba :
> yes it works on my machine,it coverts from Gregorian calendar year to
> Ethiopian calendar year.
> Swift ,C# & Java languages locally we have app to convert it, but i can't
> get it from them,it is as a commercial,Also ORACLE DB localize it.Oracle DB
>
On Tue, Dec 26, 2017 at 10:03 PM, Petr Jelinek
wrote:
> On 26/12/17 11:13, Masahiko Sawada wrote:
>> On Tue, Dec 26, 2017 at 12:49 AM, Petr Jelinek
>> wrote:
>>
It's not a problem on crash restart because StartupReorderBuffer already
does the required delete.
ReorderBuffe
yes it works on my machine,it coverts from Gregorian calendar year to
Ethiopian calendar year.
Swift ,C# & Java languages locally we have app to convert it, but i can't
get it from them,it is as a commercial,Also ORACLE DB localize it.Oracle DB
also use for commercial,
I want to Localize in Postgre
On Tue, Dec 26, 2017 at 06:37:06PM +0900, Yugo Nagata wrote:
> I have created a new entry in CF-2017-1 and registered this thread again.
Fine for me. Thanks for the update. And I guess that you are planning to
send a new version before the beginning of the next commit fest using
the feedback provi
On 26/12/17 11:13, Masahiko Sawada wrote:
> On Tue, Dec 26, 2017 at 12:49 AM, Petr Jelinek
> wrote:
>
>>>
>>> It's not a problem on crash restart because StartupReorderBuffer already
>>> does the required delete.
>>>
>>> ReorderBufferSerializeTXN, which spills the txns to disk, doesn't appear
>>>
On Tue, Dec 26, 2017 at 4:30 PM, Andres Freund wrote:
> You're proposing to lock the entire relation against many forms of concurrent
> DDL, just to get rid of that error? That seems unacceptable.
> Isn't the canonical way to solve this to take object locks?
Sure. That's where things in lmgr.c c
On Tue, 26 Dec 2017 13:51:03 +0300
Arthur Zakirov wrote:
> On Mon, Dec 25, 2017 at 05:15:07PM +0300, Aleksandr Parfenov wrote:
>
> Is I understood users need to rewrite their configurations if they
> use unaccent dictionary, for example. It is not good I think. Users
> will be upset about that i
Moin,
On Tue, December 26, 2017 5:26 am, Masahiko Sawada wrote:
> On Tue, Dec 26, 2017 at 6:19 PM, Tels
> wrote:
>> Moin,
>>
>> On Mon, December 25, 2017 7:26 pm, Masahiko Sawada wrote:
>>> On Tue, Dec 26, 2017 at 1:10 AM, Petr Jelinek
>>> wrote:
On 21/11/17 22:06, Masahiko Sawada wrote:
>>
Hi hackers,
While testing parallel hash join today, I saw a couple of errors like this:
2017-12-26 23:34:37.402 NZDT [13082] ERROR: cannot create temporary
subdirectory "base/pgsql_tmp/pgsql_tmp13080.0.sharedfileset": File
exists
There is a thinko in PathNameCreateTemporaryDir(), a new function
Fabien COELHO wrote:
> Most "permutation" functions are really cryptographic cyphers which are
> quite expensive, and require powers of two, which is not what is needed.
> ISTM that there are some constructs to deal with arbitrary sizes based on
> cryptographic functions, but that would
On Mon, Dec 25, 2017 at 05:15:07PM +0300, Aleksandr Parfenov wrote:
>
> In the current version of the patch, configurations written in old
> syntax are rewritten into the same configuration in the new syntax.
> Since new syntax doesn't support a TSL_FILTER, it was removed from the
> documentation.
On Tue, Dec 26, 2017 at 6:19 PM, Tels wrote:
> Moin,
>
> On Mon, December 25, 2017 7:26 pm, Masahiko Sawada wrote:
>> On Tue, Dec 26, 2017 at 1:10 AM, Petr Jelinek
>> wrote:
>>> On 21/11/17 22:06, Masahiko Sawada wrote:
After investigation, I found out that my previous patch was wrong
>
On Tue, Dec 26, 2017 at 12:49 AM, Petr Jelinek
wrote:
> Hi,
>
> thanks for writing the patch.
>
> On 05/12/17 06:58, Craig Ringer wrote:
>> Hi all
>>
>> [...]
>>> The cause appears to be that walsender.c's ProcessRepliesIfAny writes a
>> LOG for unexpected EOF then calls proc_exit(0). But seriali
On Sat, 23 Dec 2017 09:44:30 +0900
Michael Paquier wrote:
> On Fri, Dec 22, 2017 at 04:19:46PM +0900, Yugo Nagata wrote:
> > I was busy for and I could not work on this patch. After reading the
> > previous discussion, I still think the behavior of this patch would
> > be right. So, I would like
At Fri, 22 Dec 2017 13:47:16 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
wrote in
<20171222.134716.88479707.horiguchi.kyot...@lab.ntt.co.jp>
> Anyway, I think we are reached to a consensus that the
> time-tick-based expiration is promising. So I'll work on the way
> as the first step.
So thi
Moin,
On Mon, December 25, 2017 7:26 pm, Masahiko Sawada wrote:
> On Tue, Dec 26, 2017 at 1:10 AM, Petr Jelinek
> wrote:
>> On 21/11/17 22:06, Masahiko Sawada wrote:
>>>
>>> After investigation, I found out that my previous patch was wrong
>>> direction. I should have changed XLogSendLogical() so
Hi
2017-12-26 8:23 GMT+01:00 Lelisa Diriba :
> In Ethiopia the year have 13 months and but in Gregorian calendar the year
> have 12 months,
> The Ethiopian society's are want to use his Ethiopian calendar year,i have
> the algorithm,
> but the way i add to the postgresql source code as EXTENSION?
57 matches
Mail list logo
