Hi
I am working on scheduler extension for 9.5. It use bgworkers intensively
for any task. This is reason, why I need to decrease a log level - and I am
thinking so parallel computing needs it due high number of created and
finished workers.
It should be fixed in 9.5 - because it is limiting fact
On Sun, Jun 14, 2015 at 12:30 PM, Bruce Momjian wrote:
> On Sun, Jun 14, 2015 at 11:44:25AM +0900, Tatsuo Ishii wrote:
>> The real question here is, if contributors are required to show their
>> "official" names (along with their alias or nickname if any). If yes,
>> it is apparent that all contri
On Sun, Jun 14, 2015 at 11:44:25AM +0900, Tatsuo Ishii wrote:
> The real question here is, if contributors are required to show their
> "official" names (along with their alias or nickname if any). If yes,
> it is apparent that all contributor names should be shown in a unified
> formal style.
>
On Sun, Jun 14, 2015 at 11:38 AM, Thom Brown wrote:
> As you can see, 3 indexes are missing, which happen to be ones that
> would duplicate the column definition of another index. Is this
> intentional? If so, shouldn't it be documented behaviour?
Looking at the code (transformIndexConstraints
> Bruce Momjian wrote:
>> I have committed the first draft of the 9.5 release notes. You can view
>> the output here:
>>
>> http://momjian.us/pgsql_docs/release-9-5.html
>
> I noticed something while reading this and would like the input of our
> Japanese contributors.
>
> Normally, wester
Hi all,
I've noticed that LIKE tablename INCLUDING INDEXES skips any indexes
that were duplicated.
e.g.
CREATE TABLE people (id int, alias text);
CREATE INDEX idx_people_id_1 ON people (id);
CREATE INDEX idx_people_id_2 ON people (id) WHERE id % 2 = 0;
CREATE INDEX idx_people_alias_1 ON people (
On June 13, 2015 09:30:12 PM Bruce Momjian wrote:
> Are there other countries where this would be appropriate?
I'm pretty sure Hungarian uses the family name-given name ordering, and it's
also sometimes used in French, and therefore you often see French family names
spelled in all caps.
--
> On Sat, Jun 13, 2015 at 08:18:26PM -0300, Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > I have committed the first draft of the 9.5 release notes. You can view
> > > the output here:
> > >
> > > http://momjian.us/pgsql_docs/release-9-5.html
> >
> > I noticed something while reading this
Bruce Momjian wrote:
> On Sat, Jun 13, 2015 at 08:20:48PM -0300, Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > I have committed the first draft of the 9.5 release notes. You can view
> > > the output here:
> > >
> > > http://momjian.us/pgsql_docs/release-9-5.html
> >
> > One more thing
On Sat, Jun 13, 2015 at 08:18:26PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I have committed the first draft of the 9.5 release notes. You can view
> > the output here:
> >
> > http://momjian.us/pgsql_docs/release-9-5.html
>
> I noticed something while reading this and would l
On Sat, Jun 13, 2015 at 03:53:43PM -0700, Peter Geoghegan wrote:
> On Thu, Jun 11, 2015 at 1:23 PM, Peter Geoghegan wrote:
> > I'm not sure if it's worth mentioning the "cheap equality for text"
> > commit (e246b3d6eac09). I guess that it probably is, because it will
> > help with things like inde
On Sat, Jun 13, 2015 at 08:20:48PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I have committed the first draft of the 9.5 release notes. You can view
> > the output here:
> >
> > http://momjian.us/pgsql_docs/release-9-5.html
>
> One more thing on names. You have Alexander Shulg
On Sat, Jun 13, 2015 at 07:52:22AM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I have committed the first draft of the 9.5 release notes. You can view
> > the output here:
> >
> > http://momjian.us/pgsql_docs/release-9-5.html
> >
> > and it will eventually appear here:
> >
>
On Sat, Jun 13, 2015 at 05:47:59AM -0300, Alvaro Herrera wrote:
> Petr Jelinek wrote:
> > Hi,
> >
> > +
> > +
> > +Add JSONB functions jsonb_set() and
> > +jsonb_pretty (Dmitry Dolgov, Andrew Dunstan)
> > +
> > +
> >
> > I believe I should be 3rd author f
On Sat, Jun 13, 2015 at 08:25:55AM +0530, Amit Kapila wrote:
> On Sat, Jun 13, 2015 at 7:47 AM, Bruce Momjian wrote:
> >
> > On Thu, Jun 11, 2015 at 09:02:35PM +0200, Magnus Hagander wrote:
> > > On Thu, Jun 11, 2015 at 8:56 PM, Josh Berkus wrote:
> > >
> > > On 06/10/2015 09:50 PM, Amit Kapi
Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
One more thing on names. You have Alexander Shulgin as Alex Shulgin in
the second place his name appears. Also, since he mov
Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
I noticed something while reading this and would like the input of our
Japanese contributors.
Normally, western names are wri
On Thu, Jun 11, 2015 at 1:23 PM, Peter Geoghegan wrote:
> I'm not sure if it's worth mentioning the "cheap equality for text"
> commit (e246b3d6eac09). I guess that it probably is, because it will
> help with things like index scans, too. Arguably that isn't a sorting
> thing (it's certainly not *
> Emre Hasegeli just pointed out to me that this patch introduced
> box_contain_pt() and in doing so used straight C comparison (<= etc)
> instead of FPlt() and friends. I would think that that's a bug and
> needs to be changed -- but certainly not backpatched, because gist
> indexes would/might b
>> The related source code comment says
>>
>> /*
>> * Get any missing history files. We do this always, even when we're
>> * not interested in that timeline, so that if we're promoted to
>> * become the master later on, we don't select the same timeline that
>>
Alvaro Herrera writes:
> Tom Lane wrote:
>> I can't help thinking that this could tie in with the storage level API
>> that I was waving my arms about last year. Or maybe not --- the goals
>> are substantially different --- but I think we ought to reflect on that
>> rather than just doing a narro
Tom Lane wrote:
> I can't help thinking that this could tie in with the storage level API
> that I was waving my arms about last year. Or maybe not --- the goals
> are substantially different --- but I think we ought to reflect on that
> rather than just doing a narrow hack for column stores used
Bruce Momjian wrote:
> I have committed the first draft of the 9.5 release notes. You can view
> the output here:
>
> http://momjian.us/pgsql_docs/release-9-5.html
>
> and it will eventually appear here:
>
> http://www.postgresql.org/docs/devel/static/release.html
>
> I am re
Petr Jelinek wrote:
> Hi,
>
> +
> +
> +Add JSONB functions jsonb_set() and
> +jsonb_pretty (Dmitry Dolgov, Andrew Dunstan)
> +
> +
>
> I believe I should be 3rd author for this one as I rewrote large parts of
> this functionality as part of the review.
A
Sorry; Because some misconfiugration vacuum and analyze were'nt working.
Now I'm getting better numbers for BRIN indexes where there are zero rows
to match.
El sáb., 13 jun. 2015 a las 3:17, deavid ()
escribió:
> So I just ran a test case for hash, btree, gin_btree and brin indexes.
> Also withou
On Sat, Jun 13, 2015 at 12:02:40AM -0400, Tom Lane wrote:
> But having said that, I would not be in a hurry to remove any existing
> if-guards for the case. For one thing, it makes the code look more
> similar to backend code that uses palloc/pfree, where we do *not* allow
> pfree(NULL). There's
26 matches
Mail list logo
