On Thu, Aug 21, 2014 at 01:33:38AM +0200, Andres Freund wrote:
> On 2014-07-25 18:29:53 -0400, Tom Lane wrote:
> > > * QNX lacks sigaction SA_RESTART: I modified "src/include/port.h"
> > > to define macros to retry system calls upon EINTR (open,read,write,...)
> > > when compiled on QNX
>
On Thu, Aug 21, 2014 at 3:00 PM, Etsuro Fujita
wrote:
> (2014/08/21 13:21), Ashutosh Bapat wrote:
>
>> On Wed, Aug 20, 2014 at 3:25 PM, Etsuro Fujita
>> mailto:fujita.ets...@lab.ntt.co.jp>> wrote:
>>
>
> Hi Ashutish,
>>
>
> I am sorry that I mistook your name's spelling.
>
> (2014/08/14
> Thank you for updating the patch.
> I reviewed the patch.
>
> First of all, I think that we should not append the above message to
> section of '-r' option.
> (Or these message might not be needed at all) Whether flush location in
> feedback message is valid, is not depend on '-r' option.
>
>
On Thu, Aug 21, 2014 at 3:44 PM, Amit Kapila
wrote:
>
> On Tue, Aug 19, 2014 at 9:51 AM, Amit Kapila
wrote:
> > On Mon, Aug 18, 2014 at 7:50 PM, Heikki Linnakangas <
hlinnakan...@vmware.com> wrote:
> > >Wouldn't it make a lot more sense to create it correctly in the first
place?
> >
> > Looking a
Noah Misch wrote:
> I'm anticipating a bug report along these lines:
>
> I saw poor estimates involving a child foreign table, so I ran "ANALYZE
> VERBOSE", which reported 'INFO: analyzing "public.parent" inheritance
> tree'. Estimates remained poor, so I scratched my head for awhile befo
Em sexta-feira, 22 de agosto de 2014, Alvaro Herrera <
alvhe...@2ndquadrant.com> escreveu:
> Fabrízio de Royes Mello wrote:
>
> > I forgot to mention... I did again a lot of tests using different
> > replication scenarios to make sure all is ok:
> > - slaves async
> > - slaves sync
> > - cascade s
Fabrízio de Royes Mello wrote:
> I forgot to mention... I did again a lot of tests using different
> replication scenarios to make sure all is ok:
> - slaves async
> - slaves sync
> - cascade slaves
On v13 you mean?
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Develop
Hi Dave and Andrew,
I recently noticed the thread
[BUGS] BUG #11039: installation fails when trying to install C++
redistributable .
Unfortunately I have no XP machine at hand and can't test the
installer by myself.
Looking at the binaries in the package, they seem to be built using
Visual Stu
On Thu, Aug 21, 2014 at 09:18:22AM -0400, Andrew Dunstan wrote:
>
> On 08/15/2014 11:00 PM, Noah Misch wrote:
> >On Fri, Aug 15, 2014 at 12:49:36AM -0700, Michael Paquier wrote:
> >>Btw, how do you determine if MSVC is using HAVE_GETADDRINFO? Is it
> >>decided by the inclusion of getaddrinfo.c in
On Thu, Aug 21, 2014 at 10:26 PM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
>
>
> On Thu, Aug 21, 2014 at 8:04 PM, Alvaro Herrera
wrote:
> > Andres Freund wrote:
> >
> > > Have you looked at the correctness of the patch itself? Last time I'd
> > > looked it has fundamental correctn
On Wed, Aug 20, 2014 at 08:11:01PM +0900, Etsuro Fujita wrote:
> (2014/07/02 11:23), Noah Misch wrote:
> >Your chosen ANALYZE behavior is fair, but the messaging from a database-wide
> >ANALYZE VERBOSE needs work:
> >
> >INFO: analyzing "test_foreign_inherit.parent"
> >INFO: "parent": scanned 1 o
Heikki,
* Heikki Linnakangas (hlinnakan...@vmware.com) wrote:
> On 08/19/2014 04:27 AM, Brightwell, Adam wrote:
> >This is a "proof-of-concept" patch for a new model around role attributes
> >and fine grained permissions meant to alleviate the current over dependence
> >on superuser.
>
> Hmm. How
> "Stephen" == Stephen Frost writes:
>>> I'm inclined to think that the audience for this is far larger
>>> than the audience for the cube extension, which I have not once
>>> encountered in the field.
Stephen> +1
Most of my encounters with cube have been me suggesting it to people
on I
On Thu, Aug 21, 2014 at 8:04 PM, Alvaro Herrera
wrote:
> Andres Freund wrote:
>
> > Have you looked at the correctness of the patch itself? Last time I'd
> > looked it has fundamental correctness issues. I'd outlined a possible
> > solution, but I haven't looked since.
>
> Yeah, Fabrizio had it pa
Hi Marko,
I took a quick look at your patch at
http://www.postgresql.org/message-id/53edbcf0.9070...@joh.to (sorry I
didn't reply directly as I didn't have the message). It applies
cleanly, builds, and the tests pass. I will hopefully have more to
say after I've poked at it and understood it bet
On Tue, Mar 18, 2014 at 09:11:46AM -0400, Robert Haas wrote:
> On Mon, Mar 17, 2014 at 10:27 PM, Michael Paquier
> wrote:
> > On Tue, Mar 18, 2014 at 10:24 AM, Fabrízio de Royes Mello
> > wrote:
> >>
> >> On Thu, Mar 13, 2014 at 10:22 AM, Robert Haas
> >> wrote:
> >>> Well, it's fairly harmless
Alvaro,
* Alvaro Herrera (alvhe...@2ndquadrant.com) wrote:
> ALTER TABLE ALL IN TABLESPACE xyz
> which AFAICS should work since ALL is already a reserved keyword.
Pushed to master and REL9_4_STABLE. Apologies on it taking so long-
things have a bit "interesting" for me over the past month or two
On 2014-07-06 16:58:33 -0400, Robert Haas wrote:
> On Thu, Jul 3, 2014 at 9:03 AM, Fujii Masao wrote:
> > On Thu, Jul 3, 2014 at 4:26 AM, Andres Freund
> > wrote:
> >> Hi,
> >> Fujii noticed that I'd used
> >> \echo Use "CREATE EXTENSION pg_buffercache" to load this file. \quit
> >> in an extens
On Thu, Aug 21, 2014 at 06:15:33PM -0400, Stephen Frost wrote:
> * Tom Lane (t...@sss.pgh.pa.us) wrote:
> > Andrew Dunstan writes:
> > > I'm inclined to think that the audience for this is far larger than the
> > > audience for the cube extension, which I have not once encountered in
> > > the f
Tom Lane wrote:
> Alvaro Herrera writes:
> > Agreed. I am going over this patch, and the last bit I need to sort out
> > is the wording of these messages. I have temporarily settled on this:
>
> > ereport(ERROR,
> > (errcode(ERRCODE_INVALID_TABLE_DEFINITION),
> >
On Tue, Mar 4, 2014 at 04:52:56PM +0100, Pavel Raiskup wrote:
> Hello,
>
> RFE: Consider that you want to run pg_upgrade via some script with some
> default '-o' option. But then you also want to give the script's user a
> chance to specify the old-server's options according user's needs.
> The
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Andrew Dunstan writes:
> > I'm inclined to think that the audience for this is far larger than the
> > audience for the cube extension, which I have not once encountered in
> > the field.
+1
> Perhaps so. I would really prefer not to have to get into e
On 2014-07-02 08:55:05 +, Rajeev rastogi wrote:
> Also can we change the description of function "pg_buffercache_pages" to
> include pinning_backend also in the description.
I'm not sure what you mean here - I've adjusted the docs to include the
column? Or do you mean that it errorneously was
On 08/20/2014 03:42 PM, Arthur Silva wrote:
> What data are you using right now Josh?
The same data as upthread.
Can you test the three patches (9.4 head, 9.4 with Tom's cleanup of
Heikki's patch, and 9.4 with Tom's latest lengths-only) on your workload?
I'm concerned that my workload is unusual
On 2014-08-21 16:59:17 -0400, Alvaro Herrera wrote:
> Heikki Linnakangas wrote:
>
> > In Postgres internals slang, non-permanent means temporary or
> > unlogged. But I agree we shouldn't expose users to that term; we use
> > it in the docs, and it's not used in command names either.
>
> Agreed.
Alvaro Herrera writes:
> Agreed. I am going over this patch, and the last bit I need to sort out
> is the wording of these messages. I have temporarily settled on this:
> ereport(ERROR,
> (errcode(ERRCODE_INVALID_TABLE_DEFINITION),
>errmsg("ca
Andrew Dunstan writes:
> I'm inclined to think that the audience for this is far larger than the
> audience for the cube extension, which I have not once encountered in
> the field.
Perhaps so. I would really prefer not to have to get into estimating
how many people will be inconvenienced how
Heikki Linnakangas wrote:
> In Postgres internals slang, non-permanent means temporary or
> unlogged. But I agree we shouldn't expose users to that term; we use
> it in the docs, and it's not used in command names either.
Agreed. I am going over this patch, and the last bit I need to sort out
is
Peter Eisentraut-2 wrote
> On 8/21/14 11:16 AM, Tom Lane wrote:
>> Heikki Linnakangas <
> hlinnakangas@
> > writes:
>>> The patch also rounds a zero up to one. A naked zero with no unit is not
>>> affected, but e.g if you have "log_rotation_age=0s", it will not disable
>>> the feature as you mi
On 08/21/2014 02:48 PM, Merlin Moncure wrote:
Basically, I'm afraid that unilaterally renaming cube is going to break
enough applications that there will be more people who flat out don't
want this patch than there will be who get benefit from it, and we end
up voting to revert the feature alto
ISTM that it may be more helful to do:
ifndef JADE
#error "no jade found on your system, cannot generate the documention"
endif
We could use $(missing) for that, which is already used for bison, flex,
and perl.
I'm fine with "$(missing)" or whatever else that provides a clear message.
It is only run when the build is via XML/XSLT, not via SGML/DSSSL
(because the SGML/DSSSL build already checks the validity anyway).
I'm confused. I thought the point of this change was mostly that the
SGML toolchain is less strict than the XML toolchain, and you wanted
to have the more-stric
On 8/21/14 4:00 PM, Tom Lane wrote:
>> It is only run when the build is via XML/XSLT, not via SGML/DSSSL
>> (because the SGML/DSSSL build already checks the validity anyway).
>
> I'm confused. I thought the point of this change was mostly that the
> SGML toolchain is less strict than the XML tool
On Thu, Aug 21, 2014 at 10:07 PM, Tom Lane wrote:
> Bruce Momjian writes:
>> I tried writing the
>> query to use CTEs (second patch), but I would then have to have one
>> query for 8.3, which doesn't support CTEs, and another for 8.4+, plus
>> the CTE query was more complex than I liked. Another
Bruce Momjian writes:
> Specifically, the first attached patch causes pg_upgrade_support
> functions to throw errors when called by a backend that is not in binary
> upgrade mode. (This seems like a good safety measure.)
Agreed about that part.
> Second, and
> more importantly, the patch preven
Peter Eisentraut writes:
> We could use $(missing) for that, which is already used for bison, flex,
> and perl.
+1 ... I'm surprised it's not like that already. Fabien's quite right to
complain that the Makefile has no business inserting defaults for things
configure couldn't find.
On 8/21/14 11:16 AM, Tom Lane wrote:
> Heikki Linnakangas writes:
>> The patch also rounds a zero up to one. A naked zero with no unit is not
>> affected, but e.g if you have "log_rotation_age=0s", it will not disable
>> the feature as you might expect, but set it to 1 minute. Should we do
>> s
Peter Eisentraut writes:
> On 8/21/14 5:12 AM, Fabien COELHO wrote:
>> However, it seems that it is not run for target "html", nor for pdf/ps
>> targets. I'm wondering whether it is an oversight or if there is a
>> reason for that. Maybe the intention is that an explicit "htmlhelp" is
>> expected
On Tue, Aug 19, 2014 at 7:33 AM, Fujii Masao wrote:
> On Fri, Aug 15, 2014 at 4:30 AM, Robert Haas wrote:
>> On Wed, Aug 13, 2014 at 6:42 AM, Fujii Masao wrote:
>>> I'd propose the attached WIP patch which allows us to enable WAL archiving
>>> even in standby. The patch adds "always" as the vali
On 8/21/14 5:12 AM, Fabien COELHO wrote:
> Also, a general comment, which is independent of this patch: I found the
> documentation build especially not resilient, with a lack of clear error
> messages when something is broken. Basically, if configure does not
> found something for the doc (openjad
On 8/21/14 5:12 AM, Fabien COELHO wrote:
>
> However, it seems that it is not run for target "html", nor for pdf/ps
> targets. I'm wondering whether it is an oversight or if there is a
> reason for that. Maybe the intention is that an explicit "htmlhelp" is
> expected to do the checking, but then
On Thu, Aug 21, 2014 at 11:43:42AM -0700, David G Johnston wrote:
> Bruce Momjian wrote
> > I had to make an exception for temporary tables because pg_upgrade uses
> > temporary tables to collect schema information. I tried writing the
> > query to use CTEs (second patch), but I would then have to
On 08/21/2014 05:04 PM, Thom Brown wrote:
On 21 August 2014 14:45, Fabrízio de Royes Mello
wrote:
On Thu, Aug 21, 2014 at 5:23 AM, Christoph Berg wrote:
Re: Thom Brown 2014-08-20
7u7tsgl4s5jh1a+shq_ny7gorzc_g_yj7...@mail.gmail.com>
"ERROR: table test is not permanent"
Perhaps this would
On Thu, Aug 21, 2014 at 1:13 PM, Tom Lane wrote:
> Andrew Gierth writes:
>> "Tom" == Tom Lane writes:
>> Tom> I wonder if you've tried hard enough to avoid reserving the keyword.
>
>> GROUP BY cube(a,b) is currently legal syntax and means something completely
>> incompatible to what the spec r
Bruce Momjian wrote
> I had to make an exception for temporary tables because pg_upgrade uses
> temporary tables to collect schema information. I tried writing the
> query to use CTEs (second patch), but I would then have to have one
> query for 8.3, which doesn't support CTEs, and another for 8.4
Andrew Gierth writes:
> "Tom" == Tom Lane writes:
> Tom> I wonder if you've tried hard enough to avoid reserving the keyword.
> GROUP BY cube(a,b) is currently legal syntax and means something completely
> incompatible to what the spec requires.
Well, if there are any extant applications that
Baker, Keith [OCDUS Non-J&J] wrote:
> About configure:
>
> "./configure" barked at 2 things on QNX, and it advised using both
> "--without-readline --disable-thread-safety".
> I can investigate further, but I have been focusing on the bigger issues
> first.
I don't think th
On Tue, Feb 25, 2014 at 05:05:09PM -0800, Josh Berkus wrote:
> On 02/25/2014 04:42 PM, Bruce Momjian wrote:
> > On Tue, Feb 25, 2014 at 06:41:26PM -0500, Tom Lane wrote:
> >> I'm not sure what "many limitations" you think pg_dumpall has that pg_dump
> >> doesn't.
> >>
> >> I do think that it might
2014-08-21 17:58 GMT+02:00 Andrew Gierth :
> > "Tom" == Tom Lane writes:
>
> >> I agree, the contrib/cube patch as posted is purely so we could test
> >> everything without having to argue over the new name first.
>
> Tom> I wonder if you've tried hard enough to avoid reserving the keyword
> "Tom" == Tom Lane writes:
>> I agree, the contrib/cube patch as posted is purely so we could test
>> everything without having to argue over the new name first.
Tom> I wonder if you've tried hard enough to avoid reserving the keyword.
GROUP BY cube(a,b) is currently legal syntax and m
Hello Andres,
Thanks for your response.
About SA_RESTART:
I would like to offer you a different perspective which may alter your current
opinion.
I believe the port.h QNX macro replacement for SA_RESTART is still a reasonable
solution on QNX for these reasons:
First, I
Heikki Linnakangas writes:
> The patch also rounds a zero up to one. A naked zero with no unit is not
> affected, but e.g if you have "log_rotation_age=0s", it will not disable
> the feature as you might expect, but set it to 1 minute. Should we do
> something about that?
That sounds like a de
Now that everyone is happy with how pg_upgrade_support uses global
variables to set preserved oids (or at least has no better ideas), I
think it is time to lock down this usage to prevent future breakage.
Specifically, the first attached patch causes pg_upgrade_support
functions to throw errors wh
2014-08-21 17:00 GMT+02:00 Tom Lane :
> Andrew Gierth writes:
> > "Heikki" == Heikki Linnakangas writes:
> > Heikki> I think we should bite the bullet and rename the extension,
>
> > I agree, the contrib/cube patch as posted is purely so we could test
> > everything without having to argue over
> "Heikki" == Heikki Linnakangas writes:
Heikki> Uh, that's ugly. The EXPLAIN out I mean; as an implementation
Heikki> detail chaining the nodes might be reasonable. But the above
Heikki> gets unreadable if you have more than a few grouping sets.
It's good for highlighting performance iss
Andrew Gierth writes:
> "Heikki" == Heikki Linnakangas writes:
> Heikki> I think we should bite the bullet and rename the extension,
> I agree, the contrib/cube patch as posted is purely so we could test
> everything without having to argue over the new name first.
I wonder if you've tried har
Jeevan Chalke wrote:
> I have initialize cur_lineno to UINTMAX - 2. And then observed following
> behaviour to check wrap-around.
>
> postgres=# \set PROMPT1 '%/[%l]%R%# '
> postgres[18446744073709551613]=# \set PROMPT2 '%/[%l]%R%# '
> postgres[18446744073709551613]=# select
> postgres[1844674407
On 21 August 2014 14:45, Fabrízio de Royes Mello
wrote:
>
> On Thu, Aug 21, 2014 at 5:23 AM, Christoph Berg wrote:
> >
> > Re: Thom Brown 2014-08-20 7u7tsgl4s5jh1a+shq_ny7gorzc_g_yj7...@mail.gmail.com>
> > > "ERROR: table test is not permanent"
> > >
> > > Perhaps this would be better as "tabl
On Thu, Aug 21, 2014 at 5:23 AM, Christoph Berg wrote:
>
> Re: Thom Brown 2014-08-20
> > "ERROR: table test is not permanent"
> >
> > Perhaps this would be better as "table test is unlogged" as "permanent"
> > doesn't match the term used in the DDL syntax.
>
> I was also wondering that, but then
On 08/15/2014 11:00 PM, Noah Misch wrote:
On Fri, Aug 15, 2014 at 12:49:36AM -0700, Michael Paquier wrote:
Btw, how do you determine if MSVC is using HAVE_GETADDRINFO? Is it
decided by the inclusion of getaddrinfo.c in @pgportfiles of
Mkvdbuild.pm?
src/include/pg_config.h.win32 dictates it, an
On 07/10/2014 09:52 AM, Tomonari Katsumata wrote:
Hi,
Several couple weeks ago, I posted a mail to pgsql-doc.
http://www.postgresql.org/message-id/53992ff8.2060...@po.ntts.co.jp
In this thread, I concluded that it's better to
round up the value which is less than its unit.
Current behavior (rou
On 08/21/2014 02:09 PM, Marko Tiikkaja wrote:
On 8/21/14, 1:19 PM, Heikki Linnakangas wrote:
On 08/07/2014 01:11 AM, Marko Tiikkaja wrote:
On 7/21/14, 10:56 PM, I wrote:
Here's a patch which allows you to notice those annoying bugs with INTO
slightly more quickly. Adding to the next commit ph
On 8/21/14, 1:19 PM, Heikki Linnakangas wrote:
On 08/07/2014 01:11 AM, Marko Tiikkaja wrote:
On 7/21/14, 10:56 PM, I wrote:
Here's a patch which allows you to notice those annoying bugs with INTO
slightly more quickly. Adding to the next commit phest.
New version, fixed bugs with set operati
On 08/21/2014 01:28 PM, Andrew Gierth wrote:
A progress update:
Atri> We envisage that handling of arbitrary grouping sets will be
Atri> best done by having the planner generating an Append of
Atri> multiple aggregation paths, presumably with some way of moving
Atri> the original input
I do not understand why the last sentence in the first paragraph about
bitwise ops is put there with rounding issues, which seem unrelated. It
seems to me that it belongs to the second paragraph which is about
bitwise operators.
That's the part which came from Josh Berkus. We discussed this
A progress update:
Atri> We envisage that handling of arbitrary grouping sets will be
Atri> best done by having the planner generating an Append of
Atri> multiple aggregation paths, presumably with some way of moving
Atri> the original input path to a CTE. We have not really explored
Atri>
On 08/21/2014 11:53 AM, Fabien COELHO wrote:
attached is a small patch which updates doc/src/sgml/func.sgml. The
change explains that functions like round() and others might behave
different depending on your operating system (because of rint(3)) and
that this is according to an IEEE standard.
On 08/07/2014 01:11 AM, Marko Tiikkaja wrote:
On 7/21/14, 10:56 PM, I wrote:
Here's a patch which allows you to notice those annoying bugs with INTO
slightly more quickly. Adding to the next commit phest.
New version, fixed bugs with set operations and VALUES lists.
Looks good.
It seems we
On Tue, Aug 19, 2014 at 9:51 AM, Amit Kapila
wrote:
> On Mon, Aug 18, 2014 at 7:50 PM, Heikki Linnakangas <
hlinnakan...@vmware.com> wrote:
> >Wouldn't it make a lot more sense to create it correctly in the first
place?
>
> Looking at the code, I think it is very well possible to create
> it corre
attached is a small patch which updates doc/src/sgml/func.sgml. The change
explains that functions like round() and others might behave different
depending on your operating system (because of rint(3)) and that this is
according to an IEEE standard. It also points out that #.5 is not always
r
(2014/07/02 11:23), Noah Misch wrote:
On Fri, Jun 20, 2014 at 05:04:06PM +0900, Kyotaro HORIGUCHI wrote:
Attached is the rebased patch of v11 up to the current master.
The rest of these review comments are strictly observations; they're not
requests for you to change the patch, but they may d
Also, a general comment, which is independent of this patch: I found the
documentation build especially not resilient, with a lack of clear error
messages when something is broken. Basically, if configure does not found
something for the doc (openjade, osx, xmllint, ...) it does not complain.
(2014/08/21 13:21), Ashutosh Bapat wrote:
On Wed, Aug 20, 2014 at 3:25 PM, Etsuro Fujita
mailto:fujita.ets...@lab.ntt.co.jp>> wrote:
Hi Ashutish,
I am sorry that I mistook your name's spelling.
(2014/08/14 22:30), Ashutosh Bapat wrote:
On Thu, Aug 14, 2014 at 10:05 AM, Ets
On Thu, Aug 21, 2014 at 2:54 PM, wrote:
>> When replication slot is not specified in pg_receivexlog, the flush
>> location in the feedback message always indicates invalid. So there seems
>> to be no need to send the feedback as soon as fsync is issued, in that
>> case.
>> How should this option
Hello Peter,
Agreed. I have committed the SGML changes that make things valid now,
but I will postpone the xmllint addition until the 9.5 branch, complete
with more documentation.
Per the above announcement, here is an updated patch, also with more
documentation and explanations.
It would e
Re: Heikki Linnakangas 2014-08-21 <53f5a2d6.2050...@vmware.com>
> >1) database and role names behave similar to SQL identifiers (case-sensitive
> >/ case-folding).
> >
> >2) users and user-groups only requires special handling and behavior as
> >follows
> > Normal user :
> > A. unquoted
Re: Thom Brown 2014-08-20
> "ERROR: table test is not permanent"
>
> Perhaps this would be better as "table test is unlogged" as "permanent"
> doesn't match the term used in the DDL syntax.
I was also wondering that, but then figured that when ALTER TABLE SET
UNLOGGED is invoked on temp tables
Hello,
Attached patch implements the following TODO item :
Track number of WAL files ready to be archived in pg_stat_archiver
However, it will track the total number of any file ready to be
archived, not only WAL files.
Please let me know what you think about it.
Regards.
--
Julien Rouhaud
ht
On Wed, 2014-08-20 at 14:32 -0400, Robert Haas wrote:
> Well, I think you're certainly right that a hash table lookup is more
> expensive than modulo on a 32-bit integer; so much is obvious. But if
> the load factor is not too large, I think that it's not a *lot* more
> expensive, so it could be w
On 07/23/2014 09:14 AM, Viswanatham kirankumar wrote:
On 16 July 2014 23:12, Tom Lane wrote
Christoph Berg writes:
Re: Viswanatham kirankumar 2014-07-16
Attached patch is implementing following TODO item Process
pg_hba.conf keywords as case-insensitive
Hmm. I see a case for accepting "ALL"
> "Heikki" == Heikki Linnakangas writes:
> On 08/13/2014 09:43 PM, Atri Sharma wrote:
>> Sorry, forgot to attach the patch for fixing cube in contrib,
>> which breaks since we now reserve "cube" keyword. Please find
>> attached the same.
Heikki> Ugh, that will make everyone using the cu
On Fri, Aug 8, 2014 at 12:32 PM, Fujii Masao wrote:
> This is not user-friendly. I'd like to propose the attached patch which
> introduces the infrastructure which allows us to specify the unit when
> setting INTEGER storage parameter like autovacuum_vacuum_cost_delay.
> Comment? Review?
This patc
On 07/07/2014 10:32 PM, Abhijit Menon-Sen wrote:
At 2014-07-07 09:48:44 +0200, and...@2ndquadrant.com wrote:
I'd suggest only defining INT64_MODIFIER here and build INT64_FORMAT,
UINT64_FORMAT ontop, in c.h.
Oh, I see. I'm sorry, I misread your earlier suggestion. Regenerated
patches attached
83 matches
Mail list logo
