Hi,
Thanks for replying. I am using the latest code that is 8.1.2. I
look at the comments of construct_md_array function. On it, it says
that NULL values are not supported. Please kindly help me out or tell
me some other way.
Thankyou.
O
Hi!
I was wondering if I can use VC compiler to compile UDF DLL ?
If yes then I am wondering why I am getting linking errors:
Compiling...
fd.c
Linking...
Creating library Debug/fd.lib and object Debug/fd.exp
fd.obj : error LNK2001: unresolved external symbol _CurrentMemoryContext
Debug/fd.dll
> I was wondering if I can use VC compiler to compile UDF DLL ?
> If yes then I am wondering why I am getting linking errors:
>
> Compiling...
> fd.c
> Linking...
>Creating library Debug/fd.lib and object Debug/fd.exp
> fd.obj : error LNK2001: unresolved external symbol
> _CurrentMemoryConte
On Mon, 2006-02-06 at 21:07 -0700, Rick Gigger wrote:
> I was thinking the exact same thing. Except the "and just fsync()
> dirty pages on commit" part. Wouldn't that actually make the
> situation worse? I thought the whole point of WAL was that it was
> more efficient to fsync all of the
Hello
there isn't other way :-). If you can, use source code from cvs and compile
postgresql.
http://www.postgresql.org/developer/sourcecode/
or you can use string array, and fictive NULL values.
Regards
Pavel Stehule
Hi,
Thanks for replying. I am using the latest code that is 8.1.2. I
Martijn van Oosterhout wrote:
> On Mon, Feb 06, 2006 at 04:45:11PM -0500, Chris Browne wrote:
>
>>Further, it appears to be AIX pre-4.3 only, when using it for dlopen()
>>replacement...
>>
>>It would be an attractive idea to have configure detect not whether
>>it's open, but rather whether it is n
Hi everybody,
for a big European picture archive ( > 2 mio pictures ) we are looking
for a developer who would like to join our team for a period of 2-3
months. The work will be based on an existing working prototype (which
is very slow at the moment).
We are located in Berlin, Germany. On s
Hi all,
I decided to start implementing a streamlined WAL shipping based standby
building procedure. My aim is fairly simple: to be able to build a
standby as automated as possible.
The ultimate simplicity would be for me:
- install postgres on the standby machine;
- create a directory for th
""Magnus Hagander"" <[EMAIL PROTECTED]>
> No, you need to use mingw to compile extensions.
I think we should write some documents on how to generate
postgres.lib from postgres.exe for VC++, Borland C++ users.
> //Magnus
>
> ---(end of broadcast)---
Csaba Nagy <[EMAIL PROTECTED]> writes:
> The procedure should be something similar to the one available today if
> you do it manually. The main difference would be that the standby
> postmaster should connect to the primary server, and get all table data
> and WAL record stream through normal data
You obviously did not read further down :-)
I was proposing a subscription system, where the slave can specify the
oldest WAL file it is interested in, and keep that up to date as it
processes them.
That could cause of course trouble if a slave dies and it won't update
the subscription, but that'
Csaba Nagy <[EMAIL PROTECTED]> writes:
> You obviously did not read further down :-)
> I was proposing a subscription system, where the slave can specify the
> oldest WAL file it is interested in, and keep that up to date as it
> processes them.
And how is that "system view" going to handle subscr
On Tue, 2006-02-07 at 16:45, Tom Lane wrote:
> Csaba Nagy <[EMAIL PROTECTED]> writes:
> > You obviously did not read further down :-)
> > I was proposing a subscription system, where the slave can specify the
> > oldest WAL file it is interested in, and keep that up to date as it
> > processes them
> > No, you need to use mingw to compile extensions.
>
> I think we should write some documents on how to generate
> postgres.lib from postgres.exe for VC++, Borland C++ users.
I was under the impression it didn't work even if you did that. But I've
never tried it...
//Magnus
-
The reason to check versions is that AIX added support for standard
dlopen at 4.3 and above, which means we don't need to use the port
routines built around the older library any more.
-rocco
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
IMHO the #1 priority in the current PITR/WAL shipping system is to make the
standby able to tolerate being shut down and restarted, i.e. actually having
a true standby mode and not the current method of doing it only on startup.
While it is a trivial thing to fool postgres into staying in startup
On Tue, Feb 07, 2006 at 10:04:38AM -0500, Seneca Cunningham wrote:
> libld.a does not provide dlopen(), libdl.a does. libld.a provides
> functions like ldopen() needed by src/backend/port/dynloader/aix.c for
> the dl*() substitutes built on AIX versions that lack dlopen and
> libdl.a, which appear
On Tue, 2006-02-07 at 16:58, Andrew Rawnsley wrote:
> IMHO the #1 priority in the current PITR/WAL shipping system is to make the
> standby able to tolerate being shut down and restarted, i.e. actually having
> a true standby mode and not the current method of doing it only on startup.
This fits n
Thanks for bringing the SQL 92 row constructor into spec for
operations involving > and <. This is just fantastic. I just
benchmarked ISAM style access to tables on multi-part keys and the
speedup is tremendous vs. the non row-constructor approach to the
problem which is tedius to write and only s
Merlin,
Thanks for bringing the SQL 92 row constructor into spec for
operations involving > and <. This is just fantastic. I just
benchmarked ISAM style access to tables on multi-part keys and the
speedup is tremendous vs. the non row-constructor approach to the
problem which is tedius to write
> Martijn van Oosterhout wrote:
>> That's kinda the point of these discussions, to answer the question:
>> what is in those libraries we need? Which symbol did we want? Rather
>> than trying to detect versions, is there some change in the library
>> (added or removed symbol) that we can base our de
Merlin Moncure <[EMAIL PROTECTED]> writes:
> Thanks for bringing the SQL 92 row constructor into spec for
> operations involving > and <. This is just fantastic.
Thought you'd like that ;-)
regards, tom lane
---(end of broadcast)--
Josh Berkus writes:
> It's esoteric enough that I don't know what you're talking about. Can
> you give us an example?
He's talking about this:
http://archives.postgresql.org/pgsql-performance/2004-07/msg00188.php
regards, tom lane
---(end of bro
Andrew Rawnsley <[EMAIL PROTECTED]> writes:
> IMHO the #1 priority in the current PITR/WAL shipping system is to make the
> standby able to tolerate being shut down and restarted, i.e. actually having
> a true standby mode and not the current method of doing it only on startup.
How is shutting dow
Hi fellows,
I'm getting problems compiling a trigger written in C (exactly the one
from the documentation), when compiling it I get the errore shwoned
here.
I think the problem might be the linker, but I don't know how to fix it.
The command that I run was:
gcc -I /usr/include/postgresql/server
> Josh Berkus writes:
>> It's esoteric enough that I don't know what you're talking about. Can
>> you give us an example?
>
> He's talking about this:
> http://archives.postgresql.org/pgsql-performance/2004-07/msg00188.php
Hmm...
So the example would be that if you have just read a record fr
On Tue, 2006-02-07 at 16:11 +0100, Csaba Nagy wrote:
> I decided to start implementing a streamlined WAL shipping based standby
> building procedure. My aim is fairly simple: to be able to build a
> standby as automated as possible.
What do you find difficult about the current method? That's got
This would apply to only a single relation, so would be just as
efficient a write to the database as to WAL. The proposed route is to
sync to the database, but not to WAL, thus halving the required I/O.
Yes, its designed for large data loads.
A question - would setting fsync=off while restorin
On Tue, 2006-02-07 at 19:45 -0400, Rodolfo Campos wrote:
> I'm getting problems compiling a trigger written in C (exactly the one
> from the documentation), when compiling it I get the errore shwoned
> here.
This question belongs elsewhere (e.g. pgsql-general) -- -hackers is for
development-relate
On Wed, Feb 08, 2006 at 09:44:24AM +0800, Christopher Kings-Lynne wrote:
> >This would apply to only a single relation, so would be just as
> >efficient a write to the database as to WAL. The proposed route is to
> >sync to the database, but not to WAL, thus halving the required I/O.
> >
> >Yes, it
> > He's talking about this:
> > http://archives.postgresql.org/pgsql-performance/2004-07/msg00188.php
>
> Hmm...
>
> So the example would be that if you have just read a record from t
> that gave you value t.a=a1, t.b=b1, t.c=c1, the next one, based on
> a,b,c, would be...
>
> select * fro
On Feb 8, 2006, at 11:17 , Merlin Moncure wrote:
The proper SQL construct without row constructor is:
select * from t where
a >= a1 and
(a > a1 or b>= b1) and
(a > a1 or b > b1 or c > c1)
order by a,b,c limit 1^ no offset necessary
confused yet?
This is interesting! Could you also
> On Feb 8, 2006, at 11:17 , Merlin Moncure wrote:
>
> > The proper SQL construct without row constructor is:
> >
> > select * from t where
> > a >= a1 and
> > (a > a1 or b>= b1) and
> > (a > a1 or b > b1 or c > c1)
> > order by a,b,c limit 1^ no offset necessary
> >
> > confused yet?
>
>
On Feb 8, 2006, at 11:35 , Merlin Moncure wrote:
On Feb 8, 2006, at 11:17 , Merlin Moncure wrote:
The proper SQL construct without row constructor is:
select * from t where
a >= a1 and
(a > a1 or b>= b1) and
(a > a1 or b > b1 or c > c1)
order by a,b,c limit 1^ no offset necessary
>> On Feb 8, 2006, at 11:17 , Merlin Moncure wrote:
>>
>> > The proper SQL construct without row constructor is:
>> >
>> > select * from t where
>> > a >= a1 and
>> > (a > a1 or b>= b1) and
>> > (a > a1 or b > b1 or c > c1)
>> > order by a,b,c limit 1^ no offset necessary
>> >
>> > confus
I did an audio interview today, and it is online now:
http://bsdtalk.blogspot.com/2006/02/bsdtalk015-interview-with-postgresql.html
--
Bruce Momjian| http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive,
Merlin Moncure <[EMAIL PROTECTED]> writes:
> IMO, the sql 92 row constructor was inserted for ISAM style key based
> table browsing without cursors...more or less a 'lost art' these days
> but still relevant. This is a key strategy in dealing with large
> tables. Blog entry is forthcoming :).
Ju
37 matches
Mail list logo
