Re: [HACKERS] Thoughts on unit testing?

On 13.08.2017 21:19, Peter Geoghegan wrote: On Thu, Aug 10, 2017 at 2:53 PM, Thomas Munro wrote: The current regression tests, isolation tests and TAP tests are very good (though I admit my experience with TAP is limited), but IMHO we are lacking support for

Re: [HACKERS] Remove 1MB size limit in tsvector

On 01.08.2017 22:00, Ildus K wrote: On Tue, 1 Aug 2017 15:33:08 -0400 Robert Haas wrote: On Tue, Aug 1, 2017 at 3:10 PM, Ildus K wrote: So this would break pg_upgrade for tsvector columns? I added a function that will convert old

Re: [HACKERS] Checksums by default?

On 21.01.2017 19:35, Tom Lane wrote: Andres Freund writes: Sure, it might be easy, but we don't have it. Personally I think checksums just aren't even ready for prime time. If we had: - ability to switch on/off at runtime (early patches for that have IIRC been posted) -

Re: [HACKERS] Checksums by default?

On 21.01.2017 19:37, Stephen Frost wrote: * Tom Lane (t...@sss.pgh.pa.us) wrote: Stephen Frost writes: Because I see having checksums as, frankly, something we always should have had (as most other databases do, for good reason...) and because they will hopefully prevent

Re: [HACKERS] kqueue

On 28.09.2016 23:39, Thomas Munro wrote: On Thu, Sep 29, 2016 at 9:09 AM, Keith Fiske wrote: On Thu, Sep 15, 2016 at 11:11 PM, Thomas Munro wrote: Ok, here's a version tweaked to use EVFILT_PROC for postmaster death detection instead of the

Re: [HACKERS] Why we lost Uber as a user

On 03.08.2016 21:05, Robert Haas wrote: On Wed, Aug 3, 2016 at 2:23 PM, Tom Lane wrote: Robert Haas writes: I don't think they are saying that logical replication is more reliable than physical replication, nor do I believe that to be true. I

Re: [HACKERS] Add generate_series(date,date) and generate_series(date,date,integer)

On 26.01.2016 07:52, Simon Riggs wrote: Imagine for example a script that in some rare cases passes happens to pass infinity into generate_series() - in that case I'd much rather error out than wait till the end of the universe. So +1 from me to checking for infinity. +1 ERROR infinite

Re: [HACKERS] Releasing in September

On 26.01.2016 02:09, Peter Eisentraut wrote: On 1/25/16 2:48 AM, Torsten Zühlsdorff wrote: Nobody, but there are different solutions. And the same solutions works different in quality and quantity in the different projects. In FreeBSD for example there is an online tool for review

Re: [HACKERS] Extracting fields from 'infinity'::TIMESTAMP[TZ]

On 09.11.2015 17:41, Tom Lane wrote: Kevin Grittner writes: On Monday, November 9, 2015 9:37 AM, Robert Haas wrote: That doesn't seem like enough consensus to commit this patch, which would change everything to +/-infinity. That particular choice

Re: [HACKERS] September 2015 Commitfest

On 05.11.2015 13:49, Craig Ringer wrote: I believe that we need to lower the barrier for testing. While I agree, I'd also like to note that formulaic testing is often of limited utility. Good testing still requires a significant investment of time and effort to understand the changes made by

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 01.10.2015 00:27, Tom Lane wrote: Josh Berkus writes: On 09/30/2015 03:10 PM, Tom Lane wrote: I'd be feeling a lot more positive about this whole thread if any people had stepped up and said "yes, *I* will put in a lot of grunt-work to make something happen here". The

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

Hello, On 29.09.2015 00:34, Tom Lane wrote: Jim Nasby writes: On 9/28/15 11:43 AM, Andres Freund wrote: It has been stated pretty clearly in this thread by a number of senior community people that we're not going to use a closed source system. GitLab OTOH is

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 29.09.2015 05:54, Tom Lane wrote: Stephen Frost writes: * Jim Nasby (jim.na...@bluetreble.com) wrote: 2 years ago is when they first released the enterprise edition, which according to [1] had "The most important new feature is that you can now add members to groups of

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 25.09.2015 10:04, Albert Cervera i Areny wrote: 2015-09-25 9:57 GMT+02:00 Torsten Zuehlsdorff <mailingli...@toco-domains.de>: On 24.09.2015 20:23, David Fetter wrote: On Thu, Sep 24, 2015 at 12:10:07PM -0600, Ryan Pedela wrote: Kam Lasater wrote: I'd suggest: Github Issues, P

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 24.09.2015 20:23, David Fetter wrote: On Thu, Sep 24, 2015 at 12:10:07PM -0600, Ryan Pedela wrote: Kam Lasater wrote: I'd suggest: Github Issues, Pivotal Tracker or Redmine (probably in that order). There are tens to hundreds of other great ones out there, I'm sure one of them would also

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 23.09.2015 20:43, Robert Haas wrote: On Wed, Sep 23, 2015 at 2:30 PM, Kam Lasater wrote: Thanks for the suggestion. However, an issue tracker is not a replacement for mailing list(s) and vice versa. They are both necessary for success. I venture to say that we are

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

On 24.09.2015 01:33, Josh Berkus wrote: On 09/23/2015 03:05 PM, Jim Nasby wrote: On 9/23/15 3:12 PM, Thomas Kellerer wrote: They also support Postgres as their backend (and you do find hints here and there that it is the recommended open source DBMS for them - but they don't explicitly state

Re: [HACKERS] Commitfest problems

On 16.12.2014 08:33, David Rowley wrote: On 16 December 2014 at 18:18, Josh Berkus j...@agliodbs.com mailto:j...@agliodbs.com wrote: Man. You're equating stuff that's not the same. You didn't get your way (and I'm tentatively on your side onthat one) and take that to imply that

Re: [HACKERS] Commitfest problems

On 17.12.2014 20:00, Stephen Frost wrote: * Jaime Casanova (ja...@2ndquadrant.com) wrote: On Tue, Dec 16, 2014 at 11:32 AM, Robert Haas robertmh...@gmail.com wrote: It has been proposed that we do a general list of people at the bottom of the release notes who helped review during that

[HACKERS] Missing IPv6 for pgbuildfarm.org

Hello, i've tried to setup a FreeBSD 10 machine as buildfarm-member. But it's an IPv6 only machine and there is no IPv6 for the homepage. Can anyone add support for IPv6 to it? Greetings, Torsten -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your