Tom Lane t...@sss.pgh.pa.us writes:
Robert Haas robertmh...@gmail.com writes:
On Tue, May 29, 2012 at 9:04 AM, Johann 'Myrkraverk' Oskarsson
joh...@2ndquadrant.com wrote:
The header file crtdefs.h in MinGW typedefs errcode which conflicts
with Postgres' elog.h.
Eep. Maybe
Hi all,
I am using MingW W64 from SVN, version 3.0 beta-ish.
There are few issues when compiling Postgres with MingW W64. There was
a patch submitted to this list in July 2011 but it does not address
these issues (that I can tell). The following applies to both 32 and 64
bit builds.
Hi all,
Why would a string comparison work in one case and not another? In
the following example, it works to compare a and b, but not a and d.
This is in a C module which calls
DirectFunctionCall2( text_le, d1, d2 );
DEBUG: Comparing a == b
DEBUG: Comparing a == d
ERROR: could not
Christopher Browne cbbro...@gmail.com writes:
On Wed, Dec 21, 2011 at 8:32 PM, Johann 'Myrkraverk' Oskarsson
joh...@2ndquadrant.com wrote:
I mean to create a typed hstore, called tstore for now. I'm open
to name suggestions. It'll only support a subset of core Postgres
types to begin
Andrew Dunstan and...@dunslane.net writes:
On 12/22/2011 10:44 AM, Tom Lane wrote:
Johann 'Myrkraverk' Oskarssonjoh...@2ndquadrant.com writes:
I mean to create a typed hstore, called tstore for now.
Um ... what is the point of this, exactly? From what I've seen,
most applications for hstore
Hi all,
I mean to create a typed hstore, called tstore for now. I'm open to
name suggestions. It'll only support a subset of core Postgres types
to begin with. Keys are always text, it's the value that's typed.
Usage is very similar to hstore; this is not a complete reference.
tstore(
Bruce Momjian br...@momjian.us writes:
Robert Haas wrote:
On Fri, Jul 29, 2011 at 11:18 AM, Johann 'Myrkraverk' Oskarsson
joh...@2ndquadrant.com wrote:
I just noticed that the USECS_* constants are not defined when
the server is compiled without integer dates and timestamps.
[snip]
I
Hi all,
I just noticed that the USECS_* constants are not defined when the server
is compiled without integer dates and timestamps.
Explicitly, timestamp.h is
#ifdef HAVE_INT64_TIMESTAMP
#define USECS_PER_DAY INT64CONST(864)
#define USECS_PER_HOUR INT64CONST(36)
#define
On Fri, 06 May 2011 20:06:04 -, Tom Lane t...@sss.pgh.pa.us wrote:
Bundling pg_config into a -libs package is probably not going to happen,
at least not on Red Hat systems, because it would create multilib issues
(ie, you're supposed to be able to install 32-bit and 64-bit libraries
On Wed, 04 May 2011 15:11:57 -, Andrew Dunstan and...@dunslane.net
wrote:
On 05/04/2011 01:25 AM, Johann 'Myrkraverk' Oskarsson wrote:
On Tue, 03 May 2011 12:40:28 -, Andrew Dunstan
and...@dunslane.net wrote:
Our Makefiles use dlltool and dllwrap to create DLLs. If you used our
Hi PostgreSQL Hackers,
When compiling PG with mingw-w64 the PGDLLEXPORT macro is blank.
Here is a patch that fixes it for me. If this is correct, I'd
appreciate it will be applied to 9.0.x as well as HEAD.
--
Johann Oskarssonhttp://www.2ndquadrant.com/|[]
PostgreSQL
On Tue, 03 May 2011 09:32:29 -, Andrew Dunstan and...@dunslane.net
wrote:
On 05/03/2011 02:46 AM, Johann 'Myrkraverk' Oskarsson wrote:
When compiling PG with mingw-w64 the PGDLLEXPORT macro is blank.
Here is a patch that fixes it for me. If this is correct, I'd
appreciate
On Tue, 03 May 2011 12:40:28 -, Andrew Dunstan and...@dunslane.net
wrote:
Our Makefiles use dlltool and dllwrap to create DLLs. If you used our
recommended build method pgxs would do lots of the work for you.
I'm not sure why you asked the mingw-w64 team about building a Postgres
Hi all,
Is it possible to add support for cross compiled PGXS modules to the
build system?
That is, when PG is cross compiled, a host-triplet-pg_config is
also built for use with external modules?
I'm not adverse to submit a patch for this myself, but would like a
pointer in the general
14 matches
Mail list logo
