Streaming replication and non-blocking I/O
in [PgSql]
|
Prev: Sought after architectures for the PostgreSQL buildfarm?
Next: [HACKERS] 答复: questions about concurrency control in Postgresql
From: Tom Lane on 15 Jan 2010 15:49 I wrote: > I think it's a tools/build process problem and should be attacked that > way. Specifically, I think you missed out $(BE_DLLLIBS) in SHLIB_LINK. We'll find out at the next mingw build... regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 15 Jan 2010 15:53 Aidan Van Dyk <aidan(a)highrise.ca> writes: > Maybe an insane question, but why can postmaster just not "exec" > walreceiver? It'd greatly complicate access to shared memory. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Heikki Linnakangas on 15 Jan 2010 16:09 Tom Lane wrote: > I wrote: >> I think it's a tools/build process problem and should be attacked that >> way. > > Specifically, I think you missed out $(BE_DLLLIBS) in SHLIB_LINK. > We'll find out at the next mingw build... Thanks. But what is BE_DLLLIBS? I can't find any description of it. I suspect the MinGW build will fail because of the missing PGDLLIMPORTs. Before we sprinkle all the global variables it touches with that, let me explain what I meant by dividing walreceiver code differently between dynamically loaded module and backend code. Right now I have to go to sleep, though, but I'll try to get back to during the weekend. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 15 Jan 2010 16:47 Heikki Linnakangas <heikki.linnakangas(a)enterprisedb.com> writes: > Tom Lane wrote: >> Specifically, I think you missed out $(BE_DLLLIBS) in SHLIB_LINK. >> We'll find out at the next mingw build... > Thanks. But what is BE_DLLLIBS? I can't find any description of it. It was the wrong theory anyway --- it already is included (in Makefile.shlib). But what it does is provide -lpostgres on platforms where that is needed, such as mingw. > I suspect the MinGW build will fail because of the missing PGDLLIMPORTs. Yeah. On closer investigation the problem seems to be -DBUILDING_DLL, which flips the meaning of PGDLLIMPORT. contrib/dblink, which surely works and has the same linkage requirements as walreceiver, does *not* use that. I've committed a patch to change that, we'll soon see if it works... > Before we sprinkle all the global variables it touches with that, let me > explain what I meant by dividing walreceiver code differently between > dynamically loaded module and backend code. Right now I have to go to > sleep, though, but I'll try to get back to during the weekend. Yeah, nothing to be done till we get another buildfarm cycle anyway. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Andrew Dunstan on 15 Jan 2010 18:30
Tom Lane wrote: >> Before we sprinkle all the global variables it touches with that, let me >> explain what I meant by dividing walreceiver code differently between >> dynamically loaded module and backend code. Right now I have to go to >> sleep, though, but I'll try to get back to during the weekend. >> > > Yeah, nothing to be done till we get another buildfarm cycle anyway. > > > I ran an extra cycle. Still a bit of work to do: <http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=dawn_bat&dt=2010-01-15%2023:04:54> cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |