Re: [GENERAL] Extension coverage

2017-08-25 Thread Michael Paquier
On Sat, Aug 26, 2017 at 2:59 AM, Gabriel Furstenheim Milerud wrote: > The I built my extension against this postgres server > >$ cd $EXTENSION_SOURCE_DIR >$ make install && make installcheck > > the extension is built fine and the test run. However, I see no

Re: [GENERAL] jdbc driver vis Release 10

2017-08-25 Thread Rob Sargent
> On Aug 25, 2017, at 5:55 PM, Dave Cramer wrote: > > There are newer versions out there! > > Dave Cramer > > da...@postgresintl.com > www.postgresintl.com > >> On 25 August 2017 at 19:53, Rob Sargent wrote: >> >> >>> On 08/25/2017 05:34 PM,

Re: [GENERAL] BDR replication port

2017-08-25 Thread Zhu, Joshua
Thanks for the idea, and that is it... it's indeed the other direction of replication was affected by blocking a port -Original Message- From: Alvaro Aguayo Garcia-Rada [mailto:aagu...@opensysperu.com] Sent: Friday, August 25, 2017 5:00 PM To: Zhu, Joshua Cc:

Re: [GENERAL] BDR replication port

2017-08-25 Thread Alvaro Aguayo Garcia-Rada
That's weird. Another idea: Do changes on that server get replicated to the other servers? I'm not sure if incomming connections are used to receive WAL or to send it. Regards, Alvaro Aguayo Jefe de Operaciones Open Comb Systems E.I.R.L. Oficina: (+51-1) 3377813 | RPM: #034252 / (+51)

Re: [GENERAL] jdbc driver vis Release 10

2017-08-25 Thread Dave Cramer
There are newer versions out there! Dave Cramer da...@postgresintl.com www.postgresintl.com On 25 August 2017 at 19:53, Rob Sargent wrote: > > > On 08/25/2017 05:34 PM, Dave Cramer wrote: > > The JDBC driver release is divorced from the server release. > > Thanks > >

Re: [GENERAL] jdbc driver vis Release 10

2017-08-25 Thread Rob Sargent
On 08/25/2017 05:34 PM, Dave Cramer wrote: The JDBC driver release is divorced from the server release. Thanks Dave Cramer da...@postgresintl.com www.postgresintl.com On 23 August 2017 at 19:33, Rob Sargent

Re: [GENERAL] jdbc driver vis Release 10

2017-08-25 Thread Dave Cramer
The JDBC driver release is divorced from the server release. Thanks Dave Cramer da...@postgresintl.com www.postgresintl.com On 23 August 2017 at 19:33, Rob Sargent wrote: > I see no mention of a new jdbc driver on the release notes for Beta 1. > Does that mean there

Re: [GENERAL] BDR replication port

2017-08-25 Thread Zhu, Joshua
Thought about that possibility, so postgres on the node with port blocked was restarted after blocking the port. -Original Message- From: Alvaro Aguayo Garcia-Rada [mailto:aagu...@opensysperu.com] Sent: Friday, August 25, 2017 3:23 PM To: Zhu, Joshua Cc:

Re: [GENERAL] BDR replication port

2017-08-25 Thread Alvaro Aguayo Garcia-Rada
Just a guess: How did you blocked the port? Depending on that, you could be blocking only new connections, but connections already established would continue to transmit data; remember BDR only reconnects when connection is lost. Alvaro Aguayo Jefe de Operaciones Open Comb Systems E.I.R.L.

[GENERAL] BDR replication port

2017-08-25 Thread Zhu, Joshua
Hi, I am experimenting how network configuration impacts BDR replication, ran into something that I can't explain, and wonder if someone can shed light. Here it goes: With a four node BDR group configured and running (all using default port 5432), I purposely blocked port 5432 on one of the

Re: [GENERAL] Get user defined type OID (PostgreSQL extension in C)

2017-08-25 Thread Peter Eisentraut
On 8/25/17 14:34, Fabiana Zioti wrote: > I'm developing an extension to PostgreSQL using C. I created a > user-defined type called geo_trajc_elem. I also created a function to > generate an array of this new type. > In this case, it is not possible to use get_fn_expr_argtype because I am > not

Re: [GENERAL] Invalid magic number 0000 in log file

2017-08-25 Thread Peter Eisentraut
On 8/25/17 14:24, Moreno Andreo wrote: > I know that's related to XLOG files, but do not have idea on how to deal > with it. I had a quick googling but found nothing but "your files are > corrupted. You'd better initdb." That's pretty much it. You might not have to initdb if you have an

Re: [GENERAL] londiste3: removing a node that does not exist

2017-08-25 Thread Willy-Bas Loos
On Thu, Jun 22, 2017 at 6:03 PM, Victor Yegorov wrote: > 2017-06-22 18:21 GMT+03:00 Willy-Bas Loos : > >> Does anyone know of a method to get rid of the bad node and the data that >> it is gathering? > > > I also do not know the correct way to achieve

Re: [GENERAL] Porting libpq to QNX 4.25

2017-08-25 Thread Adam Brusselback
> > Do you believe the only path is Windows 10? Not Peter...But I believe there are better choices considering if this has to be on any sort of network, you're going to be potentially vulnerable to any number of never-to-be-patched security holes. Using XP in this day and age is a hard argument

Re: [GENERAL] Get user defined type OID (PostgreSQL extension in C)

2017-08-25 Thread Melvin Davidson
On Fri, Aug 25, 2017 at 2:34 PM, Fabiana Zioti wrote: > > I'm developing an extension to PostgreSQL using C. I created a > user-defined type called geo_trajc_elem. I also created a function to > generate an array of this new type. > > > () > > ArrayType

Re: [GENERAL] Porting libpq to QNX 4.25

2017-08-25 Thread marcelo
Hi Peter Do you believe the only path is Windows 10? Those machines are commanding Zebra printers and collecting data in a very harsh environment. So, the cheaper, the better. Why not Linux? Simply because I have Devart's Entity Developer and linqConnect to interface with postgres and I prefer

[GENERAL] Get user defined type OID (PostgreSQL extension in C)

2017-08-25 Thread Fabiana Zioti
I'm developing an extension to PostgreSQL using C. I created a user-defined type called geo_trajc_elem. I also created a function to generate an array of this new type. () ArrayType *result_array; struct geo_trajc_elem *traje = (struct geo_trajc_elem *)palloc(sizeof(struct

Re: [GENERAL] Porting libpq to QNX 4.25

2017-08-25 Thread Peter J. Holzer
On 2017-08-22 12:57:15 -0300, marcelo wrote: > We'll replace those QNX machines with WIndows XP ones The future is already here — it's just not very evenly distributed. SCNR, hp -- _ | Peter J. Holzer| we build much bigger, better disasters now |_|_) ||

[GENERAL] Invalid magic number 0000 in log file

2017-08-25 Thread Moreno Andreo
Hi everyone,     a customer reported an issue starting Postgres on his machine after reinstalling Windows (10 before, 10 now) without formatting (so there's Windows and Windows.old) because of Windows not starting up anymore. Before this reinstallation everything was OK. Now here's the log

[GENERAL] Extension coverage

2017-08-25 Thread Gabriel Furstenheim Milerud
Hello, I'm trying to measure test coverage on an extension. I've built postgres with the --enable-coverage flag: $ cd $POSTGRES_SOURCE_DIR $ ./configure --enable-coverage $ make $ make install The I built my extension against this postgres server $ cd $EXTENSION_SOURCE_DIR

Re: [GENERAL] ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100

2017-08-25 Thread Harry Ambrose
Hi All, Sorry to open this can of worms again. However, we are still struggling with this issue across quite a large amount of our estate. >From doing some further research I stumbled across the following which seems to sum up what we are seeing quite well...

Re: [GENERAL] Out of memory/corrupted shared memory problem on server

2017-08-25 Thread Tom Lane
Johann Spies writes: > While restoring a dump from our development server (768G ram) to the > production server, (PG 9.6.3 on Debian Stretch with 128G Ram) the > refreshing of a Materialized View fails like this: > local] js@wos=# REFRESH MATERIALIZED VIEW

Re: [GENERAL] Out of memory/corrupted shared memory problem on server

2017-08-25 Thread Christoph Moench-Tegeder
## Johann Spies (johann.sp...@gmail.com): > -- > 2017-08-24 19:23:26 SAST [7532-18] LOG: server process (PID 4890) was > terminated by signal 9: Killed That looks like out-of-memory. Check the kernel log/dmesg to verify. If it's the dreaded OOM-killer, you should check your

[GENERAL] Out of memory/corrupted shared memory problem on server

2017-08-25 Thread Johann Spies
While restoring a dump from our development server (768G ram) to the production server, (PG 9.6.3 on Debian Stretch with 128G Ram) the refreshing of a Materialized View fails like this: local] js@wos=# REFRESH MATERIALIZED VIEW wos_2017_1.citation_window_mv ; server closed the connection