Tom,
Did you ever find a solution to this without updating ?
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 21 September 2017 at 13:01, Dave Cramer wrote:
> Too late I just stumbled over this as well!
>
> Dave Cramer
>
> da...@postgresintl.com
> www.postgres
> On 27 Sep 2017, at 19:47, Peter Eisentraut
> wrote:
>
> At the PGCon Developer Meeting it was agreed[0] to add a list of credits
> to the release notes, including everyone who was mentioned in a commit
> message. I have now completed that list.
Wow, it’s bigger than I expected. Thanks for
Too late I just stumbled over this as well!
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 20 September 2017 at 14:34, Tom Lane wrote:
> It seems to install some libraries that depend on
> /usr/lib/system/libsystem_darwin.dylib, which doesn't exist.
> Googling sugge
to do so.
>>>>>
>>>>
>>>> I have added this as an open item because we will have to wait to see
>>>> where we are with driver support as the release gets closer.
>>>>
>>>
>>> With the release near, I'm promotin
On Thu, Aug 17, 2017 at 2:58 PM, Tom Lane wrote:
> Dave Page writes:
> > It's ActiveState Perl 5.8.8. Printing $Config{ccflags} doesn't seem to do
> > anything, but perl -V output is below:
>
> That's weird ... you get nothing from
>
> perl -MConfig -e
26379 Fix alarm() for Windows 2003
26087 Storable 0.1 compatibility
25861 IO::File performace issue
25084 long groups entry could cause memory exhaustion
24699 ICMP_UNREACHABLE handling in Net::Ping
Built under MSWin32
Compiled at Jan 23 2007 15:57:46
@INC:
c:/perl/site/lib
c:/perl/lib
.
C:\Program Files\Microsoft Visual Studio 8\VC>
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
869>
Thanks,
Dave Cramer
;
> Well, we have various buildfarm machines running perls newer than that,
> eg, crake, with 5.24.1. So I'd say there is something busted about your
> perl installation. Perhaps leftover bits of an older version somewhere?
>
Well crake is a Fedora box - and we have no proble
log
when log_replication_commands is enabled. Passing database as the value
instructs walsender to connect to the database specified in the dbname
parameter, which will allow the connection to be used for logical
replication from that database.
Dave Cramer
On Thu, May 4, 2017 at 3:54 PM, Tom Lane wrote:
> Alvaro Herrera writes:
> > Something like the (untested) attached perhaps?
>
> Looks plausible, I'm not in a position to test though.
Sandeep/Paresh - can you test please?
--
Dave Page
Blog: http://pgsnake.blogspot.c
SQL.
> > >
> >
> > What commit added support for it?
>
> I don't think the main build mechanism requires explicit support of new
> versions. configure just checks for some prerequisites.
>
Right - and they were adjusted here: https://git.postgresql.
org/gitweb/?p=post
On Thu, Mar 30, 2017 at 2:24 PM, Simon Riggs wrote:
> On 30 March 2017 at 18:29, Simon Riggs wrote:
>
>> Moving to commit this over the next hour. Last chance...
>
> Done. Great work Dave, thanks everybody.
Thanks Simon.
--
Dave Page
Blog: http://pgsnake.blogspot.com
ir have execute permissions GRANTed to pg_monitor
12) Un-redacted use of the functions underpinning the pg_stat_* views
is available to pg_read_all_stats.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL C
ure freeze immediately thereafter. Last time around
>> we left 2 weeks between CF end and feature freeze; the previous one I
>> think we had the final CF last two months. Not stretch on indefinitely,
>> but we know the final CF for a cycle takes more effort than previous
>>
Hi
On Tue, Mar 28, 2017 at 2:22 PM, Stephen Frost wrote:
> Dave,
>
> * Dave Page (dp...@pgadmin.org) wrote:
>> OK, so before I start hacking again, here's a proposal based on my
>> understanding of folks comments, and so open questions. If I can get
>> agreem
On Tue, Mar 28, 2017 at 1:52 PM, Mark Dilger wrote:
>
>> On Mar 28, 2017, at 9:55 AM, Robert Haas wrote:
>>
>> On Tue, Mar 28, 2017 at 12:47 PM, Dave Page wrote:
>>>> I don't see any precedent in the code for having a hardcoded role, other
>>>
ead_monitoring_stats?
Thanks!
On Tue, Mar 28, 2017 at 1:37 PM, Stephen Frost wrote:
> Greetings,
>
> * Robert Haas (robertmh...@gmail.com) wrote:
>> On Tue, Mar 28, 2017 at 12:47 PM, Dave Page wrote:
>> >> I don't see any precedent in the code for having a hardcoded r
On Tue, Mar 28, 2017 at 12:55 PM, Robert Haas wrote:
> On Tue, Mar 28, 2017 at 12:47 PM, Dave Page wrote:
>>> I don't see any precedent in the code for having a hardcoded role, other
>>> than
>>> superuser, and allowing privileges based on a hardcoded test fo
On Tue, Mar 28, 2017 at 12:04 PM, Mark Dilger wrote:
>
>> On Mar 28, 2017, at 8:34 AM, Dave Page wrote:
>>
>> On Tue, Mar 28, 2017 at 11:31 AM, Peter Eisentraut
>> wrote:
>>> This patch touches the pg_buffercache and pg_freespacemap extensions,
>>&
On Tue, Mar 28, 2017 at 11:39 AM, Peter Eisentraut
wrote:
> On 3/28/17 11:34, Dave Page wrote:
>> On Tue, Mar 28, 2017 at 11:31 AM, Peter Eisentraut
>> wrote:
>>> This patch touches the pg_buffercache and pg_freespacemap extensions,
>>> but there appear to be
our or so in a new version.
Right now I'm waiting for discussion to conclude before updating the
patch again.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing
On Mon, Mar 27, 2017 at 3:51 AM, Simon Riggs wrote:
> On 25 March 2017 at 16:30, Dave Page wrote:
>
>> I believe this and other reasons we've described are exactly why other DBMS'
>> do what we're proposing.
>
> It would help review if you could show som
Hi
> On 25 Mar 2017, at 15:55, Stephen Frost wrote:
>
> Robert,
>
> * Robert Haas (robertmh...@gmail.com) wrote:
>>> On Fri, Mar 24, 2017 at 12:46 PM, Dave Page wrote:
>>>> On Fri, Mar 24, 2017 at 4:24 PM, Robert Haas wrote:
>>>> That'
ne-time thing, which makes it vastly more painful to deal with
upgrades.
>> With the approach that Dave and I are advocating, we can avoid all of
>> that. Contrib modules can bake-in GRANTs to the appropriate roles,
>> upgrades can be handled smoothly even when we add new capabi
;>>> page,
>>>> that was released in 2009. That was the oldest version I could find, so
>>>> it
>>>> might go even further back.
>>>>
>>>> Dave, do you know exactly what version of MinGW narwhal is running? And
>>>&g
e "commands/user.h"
>> @@ -6677,10 +6678,12 @@ GetConfigOption(const char *name, bool missing_ok,
>> bool restrict_superuser)
>> }
>> if (restrict_superuser &&
>> (record->flags & GUC_SUPERUSER_ONLY) &&
&g
On Wed, Mar 22, 2017 at 3:46 PM, Dave Page wrote:
> On Wed, Mar 22, 2017 at 1:15 PM, Stephen Frost wrote:
>>
>> I did specifically ask for explicit roles to be made to enable such
>> capability and that the pg_monitor role be GRANT'd those roles instead
>> of
's not been done yet.
Yeah, sorry - I missed that for pg_stat_activity. I'll update the patch.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pg
On Wed, Mar 22, 2017 at 12:55 PM, Peter Eisentraut
wrote:
> On 3/22/17 07:48, Dave Page wrote:
>> With the patch, complex monitoring systems can easily be setup with
>> something like:
>>
>> CREATE ROLE monitoring_user LOGIN;
>> GRANT pg_monitor TO monitoring_ro
On Wed, Mar 22, 2017 at 11:32 AM, Robert Haas wrote:
> On Fri, Feb 24, 2017 at 5:14 AM, Dave Page wrote:
>> - Adds a default role called pg_monitor
>> - Gives members of the pg_monitor role full access to:
>> pg_ls_logdir() and pg_ls_waldir()
>> pg
Hi
On Thu, Mar 16, 2017 at 7:04 PM, Denish Patel wrote:
> Hi Dave,
>
> The patch failed applied...
>
> patch -p1 < /home/vagrant/pg_monitor.diff
> patching file contrib/pg_buffercache/Makefile
> patching file contrib/pg_buffercache/pg_buffercache--1.2--1.3.sql
On Thu, Mar 16, 2017 at 7:05 PM, Robert Haas wrote:
> On Thu, Mar 16, 2017 at 6:09 AM, Dave Page wrote:
>> Hmm, good point. Google seems to be saying there isn't one. Patch
>> updated as you suggest (and I've added back in a function declaration
>> that got l
On Thu, Mar 16, 2017 at 9:54 AM, Thomas Munro
wrote:
> On Thu, Mar 16, 2017 at 10:40 PM, Dave Page wrote:
>>> +const int n = snprintf(NULL, 0, "%lld", attrib.st_size);
>
> I wonder what the portable printf directive is for off_t. Maybe
> better to use
Hi
On Wed, Mar 15, 2017 at 5:27 PM, Robert Haas wrote:
> On Mon, Feb 20, 2017 at 6:21 AM, Dave Page wrote:
>> Patch includes the code and doc updates.
>
> Review:
>
> +strftime(mtime, 25, "%Y-%m-%d %H:%M:%S %Z",
> localtime(&(attrib.st_ctime)));
>
You have to turn it on using the autosave parameter. it's not on by
default, and apparently not documented
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 7 March 2017 at 17:15, legrand legrand
wrote:
> Thanks !
>
> that's a very good new !
>
>
> I&
gt; JDBC has it since 9.4.1210 (2016-09-07), unless I am mistaken:
>
> https://github.com/pgjdbc/pgjdbc/commit/adc08d57d2a9726309ea80d574b1db
> 835396c1c8
I thought he meant we have to play with savepoints.
Yes, we do it for you now
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
; Currently PGPASS is in the users home directory Many JDBC applications are
in much larger apps such as tomcat, etal
this concept is a bit foreign to JDBC. That being said I don't think it's
difficult to implement. Just somewhat harder to specify
for us. psql is rather limited being a command line app which is *usually*
evoked directly from the command line.
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
+HP+vQ1LtrgbsYQ=cshzzbqyft5joy...@mail.gmail.com).
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
diff --git a/contrib/pg_buffercache/Makefile b/contrib/pg_buffercache/Makefile
index 497dbeb229
eded.
Using a scheme like that would also mean that the user is more likely
to need to manually update the role their monitoring system uses
following an upgrade.
> - Do not create our own pg_monitor but instead provide
> documentation/scripts for users to create their
Hi
On Tue, Feb 21, 2017 at 5:40 PM, Masahiko Sawada wrote:
> On Mon, Feb 20, 2017 at 8:48 PM, Dave Page wrote:
>> Further to the patch I just submitted
>> (https://www.postgresql.org/message-id/CA%2BOCxow-X%3DD2fWdKy%2BHP%2BvQ1LtrgbsYQ%3DCshzZBqyFT5jOYrFw%40mail.gmail.com)
and restore backups.
Comments?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
has a hard-coded superuser check, but have ACLs that
prevent public execution by default.
Patch includes the code and doc updates.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
diff --git a/doc/src
mailing lists for comments or suggested
changes. If you have comments, please email them to
coc-comme...@postgresql.org no later than 2017-03-05, 11:59PM GMT for
the committee to review.
Regards, Dave.
--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
--
Sent via pgsql-hackers mailing
> On 27 Jan 2017, at 17:39, Stephen Frost wrote:
>
> Greetings,
>
> * Simon Riggs (si...@2ndquadrant.com) wrote:
>>> On 27 January 2017 at 14:09, Dave Page wrote:
>>>> On Fri, Jan 27, 2017 at 1:18 PM, Simon Riggs wrote:
>>>>
>>>&
On Fri, Jan 27, 2017 at 1:18 PM, Simon Riggs wrote:
> On 27 January 2017 at 12:56, Dave Page wrote:
>
>> Probably the most common complaint I get from users
>> regarding the management & monitoring tools I work on is that they
>> have to use superuser accounts to g
ms like official advice, yet is
> potentially unsafe: "access can be given to other users via GRANT".
>
> 4. Later, work towards a patch. We have some weeks to get this right.
>
> I'm willing to spend time on workshopping this in Brussels, with any
> attendees.
I
ent & monitoring tools I work on is that they
have to use superuser accounts to get the full benefits, unlike other
DBMSs where you can create a role with just the required privileges
(or indeed, other DBMSs that ship with such roles pre-defined for
convenience).
--
Dave Page
Blog: http://pgs
Not sure you can get the exec. We are working on producing the BT from
Travis-CI or I will build and run the test locally and get the trace
Dave Cramer
On 19 January 2017 at 15:31, Craig Ringer
wrote:
>
>
> On 20 Jan. 2017 04:13, "Robert Haas" wrote:
>
> On Thu, Jan 1
= 140728909791233, hash = 0x7ffe96960d58,
match = 0x16da2d1, keycopy = 0x7ffe96960d58, alloc = 0x1703af0,
hcxt = 0x16da2d0, hctl = 0x0}
max_table_size = 117899280
requestSize =
found = 0 '\000'
Dave Cramer
On 19 January 2017 at 12:05, Dave Cra
I'll try to get the stack trace from the core dump, have to build master
first
Dave Cramer
On 19 January 2017 at 12:01, Jorge Solórzano wrote:
> Robert, the logs I get from postgres (at least the section that matters)
> is here:
> If you need something else just ask...
>
&
The travis job https://travis-ci.org/pgjdbc/pgjdbc/jobs/192517342 is seeing
a segfault when we are testing against HEAD with REPLICATION turned on.
Logs can be found here
https://drive.google.com/drive/folders/0B-Heg5ZYCWbreEE4Uk5LdnJ5eWM?usp=sharing
Regards,
Dave Cramer
tely outlast, venture-funded startups.
>
Thanks for your hard work. PostgreSQL has come a long way since then!
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
That will teach me to copy and paste a config from somewhere ...
Thanks
Dave Cramer
On 9 December 2016 at 10:43, Tom Lane wrote:
> Dave Cramer writes:
> > Looking at src/port/pg_strong_random.c this would be a bug in autoconf
>
> It looks more like self-inflicted d
--with-libraries=/usr/local/opt/openssl/lib
--with-includes=/usr/local/opt/openssl/include/ --no-create --no-recursion
I am using openssl-1.0.2j
Regards,
Dave Cramer
On 27 November 2016 at 11:29, Tom Lane wrote:
> Dave Cramer writes:
> > We are proposing changing the JDBC version from
> > 9.4. to 42.x.x
>
> > We have two issues we are trying to address here.
>
> > 1) we do not want to be tied to the server release sched
s and they see no problems.
Please speak up now if you foresee any issues with this idea.
FYI, 42 was more or less chosen at random. But it is large enough to avoid
any future conflicts with the server, and greater than 9 to avoid issues
with maven requesting things like > 9
Dave Cramer
he system now, because of how successful it has proved
> to be.
Right - we go out of our way to ensure we don't break URLs. That's why
anoncvs.postgresql.org is still actively maintained for example.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB U
djust existing
>> application.
>>
>> We could continue to accept a Python list for a plain composite type,
>> this would only affect arrays of composite types.
>>
>> I don't use PL/python much myself, so I don't feel qualified to make the
>> call, though. Any 3rd opinions?
>
>
Can't you determine the correct output based on the function output
definition ?
For instance if the function output was an array type then we would return
the list as an array
if the function output was a set of then we return tuples ?
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 27 September 2016 at 14:58, Heikki Linnakangas wrote:
> On 09/27/2016 02:04 PM, Dave Cramer wrote:
>
>> On 26 September 2016 at 14:52, Dave Cramer wrote:
>>
>>> This crashes with arrays with non-default lower bounds:
>>>>
>>>> postgres=#
On 26 September 2016 at 14:52, Dave Cramer wrote:
>
>
>
>>
>> This crashes with arrays with non-default lower bounds:
>>
>> postgres=# SELECT * FROM test_type_conversion_array_int
>> 4('[2:4]={1,2,3}');
>> INFO: ([1, 2, ], )
>> serve
e
> the comments there mixing up the "inner" and "outer" dimensions? I wonder
> if that would be easier to read, if it was written in a recursive-style,
> rather than iterative with stacks for the dimensions.
>
> Yes, it is fairly convoluted.
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 18 September 2016 at 09:27, Dave Cramer wrote:
>
> On 10 August 2016 at 01:53, Pavel Stehule wrote:
>
>> Hi
>>
>> 2016-08-03 13:54 GMT+02:00 Alexey Grishchenko :
>>
>>> On Wed, Aug 3, 2016 at 12:49 PM, Alexey Grishchenko <
>>> agrishc
Yes, this should be closed as it is contained in
https://commitfest.postgresql.org/10/697/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
is patch:
>
> 1. The implemented functionality is clearly benefit - passing MD arrays,
> pretty faster passing bigger arrays
> 2. I was able to use this patch cleanly without any errors or warnings
> 3. There is no any error or warning
> 4. All tests passed - I tested Python 2.7 and Python 3.5
> 5. The code is well commented and clean
> 6. For this new functionality the documentation is not necessary
>
> 7. I invite more regress tests for both directions (Python <-> Postgres)
> for more than two dimensions
>
> My only one objection is not enough regress tests - after fixing this
> patch will be ready for commiters.
>
> Good work, Alexey
>
> Thank you
>
> Regards
>
> Pavel
>
>
>> --
>> Best regards,
>> Alexey Grishchenko
>>
>
>
Pavel,
I will pick this up.
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
Pavel,
I will pick these up.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, Sep 9, 2016 at 2:27 PM, Tom Lane wrote:
> Dave Page writes:
>> We needed a specific version that was newer than that shipped with
>> RHEL 6 (or in EPEL) iirc.
>
> Sure hope that's not true of the currently-proposed patch :-(
Looking back at my old emails, ap
by OS, like we do
> for tzdata.
>
> (That said, just checked EDB's ICU support. We currently ship our own libicu
> there, as a part of EPAS, but I don't know the reasoning/history behind
> there.)
We needed a specific version that was newer than that shipped with
RHEL 6
t thing to do in
> a green field, but given the precedent ...
>
> regards, tom lane
>
>
> seems to me that it should report 10 for the major and whatever comes
after the . for the minor ?
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
ing to keep in mind is that both JDBC and ODBC are not exclusively
PostgreSQL drivers and as such we sometimes have to jump through hoops to
provide the semantics requested by the API.
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
7;re doing
> something very different - not necessarily wrong - and not attempt to
> impose your ideas on everyone as if it's the only true way to write a db
> driver.
>
A number of other drivers default to this behaviour, including at least
MS-SQL and Oracle. psqlODBC a
ci build) for simplified
> navigation to test results.
>
> Here's the commit: https://github.com/vlsi/postgres/commit/
> 4841f8bc00b7c6717d91f51c98979ce84b4f7df3
> Here's how test results look like: https://travis-ci.org/vlsi/postgres
>
>
Nice work +!
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
reated on github, but I don't
think there are any animals running the JDBC test suite
We can add tests, what exactly do we want to test. Then setting up an
animal to run the tests would be fairly straight forward.
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
ng jvm from sql or vice-versa is not really possible.
I do like the idea of the background worker and shared memory though.
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
ere is an issue with the Windows x64 build with the version of VC++
that's used for the installers. I believe there was a fix committed
for this yesterday by Tom.
The button was supposed to be removed until we get an updated build -
apologies for the inconvenience.
--
Dave Page
Blog: http://pgs
> On 13 May 2016, at 17:24, Magnus Hagander wrote:
>
>> On Fri, May 13, 2016 at 5:29 PM, Dave Page wrote:
>> On Fri, May 13, 2016 at 4:23 PM, Thom Brown wrote:
>> >
>> > Well, one potential issues is that there may be projects which have
>> > al
On Fri, May 13, 2016 at 5:08 PM, Bruce Momjian wrote:
> On Fri, May 13, 2016 at 12:05:34PM -0400, Stephen Frost wrote:
>> * Dave Page (dp...@pgadmin.org) wrote:
>> > I imagine the bigger issue will be apps that have been written
>> > assuming the first part of the vers
tered all over pgAdmin 3 for
example) - largely because in such apps we're almost always checking
for a version greater than or less than x.y.
I imagine the bigger issue will be apps that have been written
assuming the first part of the version number is only a single digit.
--
D
Does anyone else have a Windows 7 installation we can test this on ?
This
https://github.com/postgres-plr/plr/files/191013/plr-8.3.0.16-pg9.5-win32.zip
is actually a 64 bit version built on windows 10. I've had one confirmation
that it works.
Dave
Dave Cramer
da...@postgresint
und: C:\pgbuild\pgadmin3-jinfroster\pgAdmin3.xml.
> C:\pgbuild\pgadmin3-jinfroster\pgAdmin3.targets 45 6 pgAdmin3
Visual Studio seems to delete that file when doing a clean, for
reasons I never quite figured out. You can just check it out from the
git repo again and it should be OK.
t; PgAdmin3 using build-wxmsw.bat.
>
>
> If I remember it right for PgAdminIII needed mingw now.
> Thanks.
pgAdmin III has never supported Mingw, it's always used VC++.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
tioned to Sehrope on IRC, at least for my 2c, if you want a
> compact JSON format to reduce the amount of traffic over the wire or to
> do things with on the client side, we should probably come up with a
> binary format, rather than just hack out the whitespace. It's not like
> representing numbers using ASCII characters is terribly efficient
> either.
>
>
+1
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
That would get rid of a lot of logspam.
>
> Would that make sense?
Absolutely. It would be very nice to get rid of such noise.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via
On 3 April 2016 at 22:20, Stephen Frost wrote:
> * Craig Ringer (cr...@2ndquadrant.com) wrote:
> > On 4 April 2016 at 10:13, Dave Cramer wrote:
> > > Async notification is the easier part, I wasn't aware that the ssl
> library
> > > had this problem though
&
On 3 April 2016 at 21:56, Stephen Frost wrote:
> Dave,
>
> * Dave Cramer (p...@fastcrypt.com) wrote:
> > On 3 April 2016 at 15:35, Stephen Frost wrote:
> > > Not generally much of a JDBC user myself, but the inability to avoid
> > > polling for LISTEN notifi
On 3 April 2016 at 12:18, Igal @ Lucee.org wrote:
> On 4/3/2016 8:21 AM, Dave Cramer wrote:
>
>
> On 9 March 2016 at 20:49, Craig Ringer wrote:
>
>> On 3/8/2016 5:12 PM, Craig Ringer wrote:
>>
>>>
>>> Are there good reasons to use pgjdbc over pgj
On 3 April 2016 at 15:35, Stephen Frost wrote:
> * Dave Cramer (p...@fastcrypt.com) wrote:
> > On 9 March 2016 at 20:49, Craig Ringer wrote:
> >
> > > On 10 March 2016 at 00:41, Igal @ Lucee.org wrote:
> > >
> > >> On 3/8/2016 5:12 PM, Craig
gt;>
>>
> Maturity, support for older versions (-ng just punts on support for
> anything except new releases) and older JDBC specs, completeness of support
> for some extensions. TBH I haven't done a ton with -ng yet.
>
>
I'd like to turn this question around.
Getting lots of POSTGRESQL_TRACE_... undefined.
Any hints ?
Dave Cramer
There is an impedance mismatch between the java ecosystem and distros.
We have moved to maven as have most other java projects.
As Craig said, if you want to build it, patch it out, and create a
ant/Makefile to make the jar.
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
Per discussion at the Brussels developer meeting and within the
release team, the high level schedule for 9.6 will be:
Beta: May (before PGCon)
Release: September
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise
ort" is also entitled to
use either our 9.4 or 9.5 versions which do have JSONB support. Our
new versions are typically released within a couple of months of
PostgreSQL, and in the case of 9.5, the gap was more like 3 weeks.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @p
Hi Marko,
Interesting so why would it choose a worse plan at that point ? Why would
it change at all if the current plan is working well ?
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 12 January 2016 at 07:15, Marko Tiikkaja wrote:
> On 12/01/16 13:00, Dave Cramer wr
We have an interesting problem, and the reporter has been kind enough to
provide logs for which we can't explain.
I'd be interested to hear any plausible explanations for a prepared plan
suddenly going from 2ms to 60ms for the same input values ?
Dave Cramer
da...@postgr
tgresql.org) as an embedded
database in some applications, and for development/test. There are a
huge number of Windows PostgreSQL users out there.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Comp
On Wed, Dec 2, 2015 at 1:06 PM, Bruce Momjian wrote:
> On Wed, Dec 2, 2015 at 08:53:07AM +0000, Dave Page wrote:
>> On Tue, Dec 1, 2015 at 9:55 PM, Bruce Momjian wrote:
>> > On Tue, Dec 1, 2015 at 06:40:09PM -0300, Alvaro Herrera wrote:
>> >> Bruce Momjian wrote:
able to ensure the same binaries
would run on all the different supported versions.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.
Add
DriverManager.setLogWriter(new PrintWriter(System.out));
below the setLogLevel and it will
I'll fix this though
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 23 October 2015 at 22:35, Tatsuo Ishii wrote:
> Unfortunately it doesn't work (no debug trace).
>
This should work better
https://oss.sonatype.org/content/repositories/snapshots/org/postgresql/postgresql/9.4-1204-jdbc41-SNAPSHOT/
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 23 October 2015 at 21:32, Dave Cramer wrote:
> No, I need to provide you with a 41 version.
&g
No, I need to provide you with a 41 version.
I just happened to have java 1.8 on my machine.
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 23 October 2015 at 21:31, Tatsuo Ishii wrote:
> Dave,
>
> Thanks for the quick response. Unfortunately now I'm getting error
&
Tatsuo,
Can you confirm it is fixed in this snapshot
https://oss.sonatype.org/content/repositories/snapshots/org/postgresql/postgresql/9.4-1204-jdbc42-SNAPSHOT/
Dave Cramer
da...@postgresintl.com
www.postgresintl.com
On 23 October 2015 at 19:00, Dave Cramer wrote:
> Tatsuo,
>
> p
1 - 100 of 2214 matches
Mail list logo
