-- REVISED NOTE --
> Hm. s_lock.h does define TAS() in terms of InterlockedCompareExchange()
if WIN32_ONLY_COMPILER is defined ... but that code hasn't changed in quite
a long time. It
> seems like the combination of an extension built with WIN32_ONLY_COMPILER
and a core built without that flag
Congrats Andres!
On Fri, May 23, 2014 at 7:54 AM, Fabrízio de Royes Mello <
fabriziome...@gmail.com> wrote:
> Hi All,
>
> At the Developer Meeting that occurred 21th May 2014 was announced a new
> PostgreSQL commiter [1], Mr. Andres Freund.
>
> I had the opportunity to work and be mentored by hi
On Thu, May 22, 2014 at 11:24:47PM -0300, Fabrízio de Royes Mello wrote:
> Hi All,
>
> At the Developer Meeting that occurred 21th May 2014 was announced a new
> PostgreSQL commiter [1], Mr. Andres Freund.
>
> I had the opportunity to work and be mentored by him. He deserves very much
> this conf
On Fri, May 23, 2014 at 11:24 AM, Fabrízio de Royes Mello
wrote:
> Thank you and Congrats Andres!
+1.
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Hi All,
At the Developer Meeting that occurred 21th May 2014 was announced a new
PostgreSQL commiter [1], Mr. Andres Freund.
I had the opportunity to work and be mentored by him. He deserves very much
this confidence, for the excellent work that has been doing for the
community.
Thank you and Co
Hi,
I have two comments about 9.4 release notes.
1. typo
>Pg_upgrade now uses -U to specify the user name (Bruce Momjian)
It should be pg_upgrade.
2. undesirable link
>Allow pg_recvlogical to receive data logical decoding data (Andres Freund)
The term of "pg_recvlogical" jumps to a page of pg
Andres Freund wrote:
> On 2014-05-22 16:37:35 -0400, Tom Lane wrote:
> > We could do that ... but I wonder if we shouldn't remove assert_enabled
> > altogether. What's the use case for turning it off? Not matching the
> > speed of a non-cassert build, because for instance MEMORY_CONTEXT_CHECKING
On 2014-05-22 16:37:35 -0400, Tom Lane wrote:
> Andres Freund writes:
> > Since there seem to be multiple static checkers (coverity, clang
> > checker) having problems with assert_enabled can we just optionally
> > disable it?
> > I am thinking of replacing it by a AssertionsEnabled() macro which
On Thu, May 22, 2014 at 4:31 PM, Andres Freund wrote:
> Since there seem to be multiple static checkers (coverity, clang
> checker) having problems with assert_enabled can we just optionally
> disable it?
> I am thinking of replacing it by a AssertionsEnabled() macro which then
> is unconditionall
Andres Freund writes:
> Since there seem to be multiple static checkers (coverity, clang
> checker) having problems with assert_enabled can we just optionally
> disable it?
> I am thinking of replacing it by a AssertionsEnabled() macro which then
> is unconditionally defined when DISABLE_ENABLE_AS
Hi,
Since there seem to be multiple static checkers (coverity, clang
checker) having problems with assert_enabled can we just optionally
disable it?
I am thinking of replacing it by a AssertionsEnabled() macro which then
is unconditionally defined when DISABLE_ENABLE_ASSERT is defined.
Greetings,
On Thu, May 22, 2014 at 11:07 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Sun, May 18, 2014 at 12:28 AM, Tom Lane wrote:
>>> So, having seen that proof-of-concept, I'm wondering if we shouldn't make
>>> an effort to support contrib/uuid-ossp with a choice of UUID libraries
>>> underneath it.
On 22/05/2014 17:07, Tom Lane wrote:
> Robert Haas writes:
>> On Sun, May 18, 2014 at 12:28 AM, Tom Lane wrote:
>>> So, having seen that proof-of-concept, I'm wondering if we shouldn't make
>>> an effort to support contrib/uuid-ossp with a choice of UUID libraries
>>> underneath it. There is a n
> Hm. s_lock.h does define TAS() in terms of InterlockedCompareExchange()
if WIN32_ONLY_COMPILER is defined ... but that code hasn't changed in quite
a long time. It
> seems like the combination of an extension built with WIN32_ONLY_COMPILER
and a core built without that flag should never have
On 5/21/14, 2:37 PM, Bruce Momjian wrote:
On Wed, May 21, 2014 at 04:23:34PM -0400, Tom Lane wrote:
Bruce Momjian writes:
On Wed, May 21, 2014 at 10:56:59AM -0600, Jeff Ross wrote:
Yes, using 9.3's pg_dump of 8.4 and applying it to both an 8.4 and a
9.3 cluster, the contact_email table now
Robert Haas writes:
> On Sun, May 18, 2014 at 12:28 AM, Tom Lane wrote:
>> So, having seen that proof-of-concept, I'm wondering if we shouldn't make
>> an effort to support contrib/uuid-ossp with a choice of UUID libraries
>> underneath it. There is a non-OSSP set of UUID library functions
>> av
On Sun, May 18, 2014 at 12:28 AM, Tom Lane wrote:
> I was intending to draft something more self-contained to present to
> -hackers, but since this is where we're at ... the quoted material
> omits a couple of important points:
>
> (1) People had been working around uuid-ossp's issues on OS X by
>
Alvaro Herrera writes:
> Bruce Momjian wrote:
>> Moving forward, I think you need to add a dummy column to each problem
>> table and drop the column that will create a toast table and allow
>> you to do the upgrade. I could have pg_upgrade detect this problem, but
>> until I know the cause,
Bruce Momjian wrote:
> Moving forward, I think you need to add a dummy column to each problem
> table and drop the column that will create a toast table and allow
> you to do the upgrade. I could have pg_upgrade detect this problem, but
> until I know the cause, I don't think that is wise.
"Paragon Corporation" writes:
> Not sure if people know this, but PostGIS windows builds are built with
> mingw64-w32 and mingw64-w64 chains and usually used with EDB VC++ built
> PostgreSQL.
> This is mostly because there is too much unix stuff ingrained in PostGIS
> toolchain making it difficul
=?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= writes:
> Deadlines?
I think the plan is 1 month for each of the first 4 fests, and a bit more
for the last one (6-8 weeks maybe).
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
On Wed, May 21, 2014 at 04:37:13PM -0400, Bruce Momjian wrote:
> On Wed, May 21, 2014 at 04:23:34PM -0400, Tom Lane wrote:
> > Bruce Momjian writes:
> > > On Wed, May 21, 2014 at 10:56:59AM -0600, Jeff Ross wrote:
> > >> Yes, using 9.3's pg_dump of 8.4 and applying it to both an 8.4 and a
> > >> 9
Em quinta-feira, 22 de maio de 2014, Heikki Linnakangas <
hlinnakan...@vmware.com> escreveu:
> On 05/22/2014 07:55 AM, Fabrízio de Royes Mello wrote:
>
>> Em quinta-feira, 22 de maio de 2014, Peter Eisentraut
>> escreveu:
>>
>> For those who were not at the developer meeting, here is the commit
On 05/22/2014 07:55 AM, Fabrízio de Royes Mello wrote:
Em quinta-feira, 22 de maio de 2014, Peter Eisentraut
escreveu:
For those who were not at the developer meeting, here is the commit fest
schedule for 9.5:
June 15
August 15
October 15
December 15
February 15
beta in June 2015
Actually
Em quinta-feira, 22 de maio de 2014, Peter Eisentraut
escreveu:
> For those who were not at the developer meeting, here is the commit fest
> schedule for 9.5:
>
> June 15
> August 15
> October 15
> December 15
> February 15
>
> beta in June 2015
>
>
Actually you meant:
June 14
August 14
October 1
At 2014-05-22 07:22:42 -0400, pete...@gmx.net wrote:
>
> We need a volunteer to manage the first commit fest.
I volunteer.
-- Abhijit
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Thu, May 22, 2014 at 6:33 AM, Petr Jelinek wrote:
> On 22/05/14 06:21, Robert Haas wrote:
>> The main thing I'm not sure about is how to format the message that we
>> write to the shm_mq. One option is to try to use the good old FEBE
>> protocol. This doesn't look entirely straightforward, be
For those who were not at the developer meeting, here is the commit fest
schedule for 9.5:
June 15
August 15
October 15
December 15
February 15
beta in June 2015
The obvious change is that there will be five commit fests instead of
four. Also, the time between beta and release is planned to be
On 22/05/14 06:21, Robert Haas wrote:
The main thing I'm not sure about is how to format the message that we
write to the shm_mq. One option is to try to use the good old FEBE
protocol. This doesn't look entirely straightforward, because
send_message_to_frontend() assembles the message using p
29 matches
Mail list logo
