Em domingo, 8 de novembro de 2015, Bruce Momjian
escreveu:
> This git cartoon was too funny not to share:
>
> http://xkcd.com/1597/
>
> Maybe we need it on our git wiki page. ;-)
>
I think we need our own cartoon with a funny DB story.
--
Fabrízio de Royes Mello
Consultoria/Coachin
This git cartoon was too funny not to share:
http://xkcd.com/1597/
Maybe we need it on our git wiki page. ;-)
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roma
Am 07.11.2015 um 22:14 schrieb Tom Lane:
> Pushed. I took the opportunity to fix the const-ness annotation of the
> function result type, too.
Great, thank you!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
On Fri, Nov 6, 2015 at 4:54 AM, Ashutosh Bapat
wrote:
> PFA patch to get data sorted from the foreign server (postgres_fdw)
> according to the pathkeys useful for merge join.
An idle thought. There are going to be a lot of cases where different
software systems actually disagree about collation
"David E. Wheeler" writes:
> Apple says that the more people file bugs, the more likely the issue is to
> get attention. So by all means, please file radars about this. You can
> reference 21732670 as the bug youâre duping (they marked mine as a dupe for
> that one).
Done here.
On Nov 4, 2015, at 8:37 PM, Michael Paquier wrote:
> There is:
> http://openradar.appspot.com/22807197
Yep, I filed that because I was unable to build the DBD::Oracle Perl module,
since I can’t tell it where to find the SQL*Plus libraries. Big PITA.
Apple says that the more people file bugs, t
Julien Rouhaud writes:
> On 23/10/2015 14:59, Michael Paquier wrote:
>>> Andres Freund wrote:
FWIW, adding an <> operator for xid seems like a perfectly good
idea.
>> See for example the attached
> I just reviewed the patch, tests passed and feature works as intended.
> I change the st
Lars Kanis writes:
> Thank you for the quick response! Attached the last minute - now or
> never patch to change the function name.
Pushed. I took the opportunity to fix the const-ness annotation of the
function result type, too.
regards, tom lane
--
Sent via pgsql-ha
Lars Kanis writes:
> Thank you for the quick response! Attached the last minute - now or
> never patch to change the function name.
Ah, thanks for doing the legwork. It's pretty late in the day Heikki's
time, so I'll review and hopefully push this.
regards, tom lane
--
On 07-11-2015 12:21, Praveen M wrote:
I would like to print the raw parse tree into the log . Is there any
internal utility function to achieve this. If there is none , can you
please help me to achieve this.
debug_print_parse = on
--
Euler Taveira Timbira - http://www.ti
Tom Lane writes:
> Heikki Linnakangas writes:
>> The question is, do we want to still change it? It's a new function in
>> 9.5, and we're just about to enter beta, so I guess we could, although
>> there might already be applications out there using it. If we do want to
>> rename it, now is the
Thank you for the quick response! Attached the last minute - now or
never patch to change the function name.
In addition I perceived a small inconsistency with the naming of the
SGML id of PQsslAttribute. This is addressed in the second patch file.
--
Kind Regards,
Lars
From 5b7f116de237df540493
On Sat, Nov 7, 2015 at 7:52 PM, Bruce Momjian wrote:
> On Wed, Nov 4, 2015 at 07:58:52AM -0500, Bruce Momjian wrote:
> > [BCC to pgsql-cluster-hack...@postgresql.org]
> >
> > I have summarized the Vienna cluster summit meeting from last week by
> > adding italicized answers to the agenda questio
On Friday, November 6, 2015 3:59 PM, Robert Haas wrote:
> Modified Files
> --
> src/backend/executor/tqueue.c| 983 -
This patch created some referenced local variables:
tqueue.c: In function ‘tqueueReceiveSlot’:
tqueue.c:124:18: error: varia
2015-11-05 7:24 GMT+01:00 Catalin Iacob :
> On Wed, Nov 4, 2015 at 10:12 AM, Pavel Stehule
> wrote:
> > It helped me lot of, thank you
>
> Welcome, I learned quite some from the process as well.
>
> >>
> >>
> >> There's just the doc part left then.
> >
> >
> > done
>
> We're almost there but not
Joe Conway writes:
> On 11/07/2015 07:12 AM, Greg Stark wrote:
>> On Sat, Nov 7, 2015 at 2:32 AM, Tom Lane wrote:
>>> What I'm wondering about is whether to back-patch this.
>> I would say wrong answers are wrong answers.
> +1
Hearing no objections, done.
regards, tom
On 11/07/2015 07:12 AM, Greg Stark wrote:
> On Sat, Nov 7, 2015 at 2:32 AM, Tom Lane wrote:
>> What I'm wondering about is whether to back-patch this. It's possible
>> that people have written patterns like this and not realized that they
>> aren't doing quite what's expected. Getting a failure
On Fri, Nov 6, 2015 at 11:32 AM, Robert Haas wrote:
> On Thu, Nov 5, 2015 at 11:54 PM, Ashutosh Bapat
> wrote:
> > Hi All,
> > PFA patch to get data sorted from the foreign server (postgres_fdw)
> > according to the pathkeys useful for merge join.
> >
> > For a given base relation (extendable to
Hi,
Thank you for your feedback.
My comments are inside.
On 11/07/2015 05:11 PM, Amit Kapila wrote:
Today, while studying your proposal and related material, I noticed
that in both the approaches DTM and tsDTM, you are talking about
committing a transaction and acquiring the snapshot consistent
On Wed, Nov 4, 2015 at 07:58:52AM -0500, Bruce Momjian wrote:
> [BCC to pgsql-cluster-hack...@postgresql.org]
>
> I have summarized the Vienna cluster summit meeting from last week by
> adding italicized answers to the agenda questions, even though we didn't
> follow the agenda ;-) :
>
> h
> On Fri, Nov 6, 2015 at 9:42 AM, Kouhei Kaigai wrote:
> > This patch needs to be rebased.
> > One thing different from the latest version is fdw_recheck_quals of
> > ForeignScan was added. So, ...
> >
> > (1) Principle is that FDW driver knows what qualifiers were pushed down
> > and how does it
Hi All,
I would like to print the raw parse tree into the log . Is there any
internal utility function to achieve this. If there is none , can you
please help me to achieve this.
Thanks as always
Praveen
On Sat, Nov 7, 2015 at 2:32 AM, Tom Lane wrote:
> What I'm wondering about is whether to back-patch this. It's possible
> that people have written patterns like this and not realized that they
> aren't doing quite what's expected. Getting a failure instead might not
> be desirable in a minor rel
Hackers!
I'd like to raise a topic about extracting fields from infinite
timestamps, so much more that it is mentioned in the TODO list:
"Determine how to represent date/time field extraction on infinite
timestamps".
Currently extracting any field from 'infinity'::TIMESTAMP[TZ] gives
result "0" a
Thank you for working on this.
I tried the patch with a Turkish dictionary [1] I could find on the
Internet. It worked for some words, but not others:
> hasegeli=# create text search dictionary hunspell_tr (template = ispell,
> dictfile = tr, afffile = tr);
> CREATE TEXT SEARCH DICTIONARY
>
> h
On Sat, Nov 7, 2015 at 12:52 PM, Amit Kapila
wrote:
>
> On Sat, Nov 7, 2015 at 12:07 AM, Robert Haas
wrote:
> >
> > On the whole, I'm inclined to think that the XTM-based approach is
> > probably more useful and more general, if we can work out the problems
> > with it. I'm not sure that I'm rig
On Sat, Oct 31, 2015 at 2:52 PM, konstantin knizhnik <
k.knizh...@postgrespro.ru> wrote:
> Hi,
>
> PostgresPro cluster team wants to announce proposal for eXtensible
> Transaction Manager API and reference implementation of distributed
> transaction manager (pg_dtm).
> pg_dtm is just a standard Po
On 11/6/15 11:34 AM, Robert Haas wrote:
> On Fri, Nov 6, 2015 at 12:52 AM, Michael Paquier
> wrote:
>>> I guess I'm wondering whether there's really enough of this to need
>>> its own category.
>>
>> We have a category "Code comments" as well. Let's give it a shot so I
>> am adding it. We could al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
On 23/10/2015 14:59, Michael Paquier wrote:
> On Fri, Oct 23, 2015 at 7:20 AM, Alvaro Herrera
> wrote:
>> Andres Freund wrote:
>>
>>> FWIW, adding an <> operator for xid seems like a perfectly good
>>> idea.
>
> +1. I have wanted that more
> -Original Message-
> From: pgsql-hackers-ow...@postgresql.org
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Robert Haas
> Sent: Saturday, November 07, 2015 1:42 AM
> To: Kaigai Kouhei(海外 浩平)
> Cc: Amit Kapila; Andres Freund; pgsql-hackers
> Subject: Re: [HACKERS] CustomScan s
30 matches
Mail list logo
