Re: [HACKERS] Retiring from the Core Team

Thanks, Josh, for everything. I especially enjoyed your monthly updates at SFPUG. Cheers, Steve On Thu, Jan 12, 2017 at 1:59 PM, Merlin Moncure wrote: > On Wed, Jan 11, 2017 at 6:29 PM, Josh Berkus wrote: > > Hackers: > > > > You will have noticed that I

Re: [HACKERS] Is it time to kill support for very old servers?

This thread gets me thinking about the definition of "support." While support in practice seems to primarily relate to fixes/updates to the supported version itself it could just as well apply to interoperability support by newer versions. Given that the standard PostgreSQL upgrade process

Re: [HACKERS] Bug in to_timestamp().

On Fri, Jun 24, 2016 at 3:43 PM, Joshua D. Drake <j...@commandprompt.com> wrote: > On 06/24/2016 02:16 PM, Tom Lane wrote: > >> Robert Haas <robertmh...@gmail.com> writes: >> >>> On Fri, Jun 24, 2016 at 12:26 PM, Steve Crawford >>> <scrawf...@p

Re: [HACKERS] Bug in to_timestamp().

My observation has been that the PostgreSQL development group aims for correctness and the elimination of surprising results. This was part of the reason to eliminate a number of automatic casts to dates in earlier versions. To me, 2016-02-30 is an invalid date that should generate an error.

Re: [HACKERS] Feature request: make cluster_name GUC useful for psql prompts

connections? You can use variables to approximate the behavior of aliases so you can hack an alias that includes the reconnect and re-read. Or just \i ~/.psqlrc as you deem necessary. Cheers, Steve On Fri, May 6, 2016 at 12:50 PM, Jerry Sievers <gsiever...@comcast.net> wrote: > Steve

Re: [HACKERS] Feature request: make cluster_name GUC useful for psql prompts

d. Cheers, Steve On Fri, May 6, 2016 at 11:42 AM, Jerry Sievers <gsiever...@comcast.net> wrote: > Peter Eisentraut <peter.eisentr...@2ndquadrant.com> writes: > > > On 5/5/16 9:21 PM, Steve Crawford wrote: > > > >> Adding an escape sequence that references c

[HACKERS] Feature request: make cluster_name GUC useful for psql prompts

It's great that 9.5 has the new cluster_name variable as an available GUC. It would be even better to make that GUC available for use in psql prompting escape sequences. Prompting via sequences utilizing %M, %m and %> means the same cluster could be identified numerous ways (local, 127.0.0.1,

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

I was unaware that we had +- infinity for numeric. select pg_typeof(extract(epoch from current_date)); pg_typeof -- double precision Given that null is a "special value that is used to indicate the absence of any data value" and that attributes like month or day-of-week will

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

On Mon, Sep 28, 2015 at 4:41 PM, Jim Nasby wrote: > Note that since they also offer a hosted solution we should use that to > play with instead of trying to install it at this point. > > Integrating the issue tracker looks like it's just a call to this API: >

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

On Tue, Sep 29, 2015 at 7:16 AM, David Fetter wrote: > ...What we're not fine with is depending on a proprietary system, no > matter what type of license, as infrastructure... > > Exactly. Which is why I was warning about latching onto features only available in the closed

Re: [HACKERS] What does RIR as in fireRIRrules stand for?

Candidate for Appendix K? Cheers, Steve On Thu, Aug 27, 2015 at 6:52 AM, Tom Lane t...@sss.pgh.pa.us wrote: Andres Freund and...@anarazel.de writes: On 2015-08-27 09:43:09 -0400, Tom Lane wrote: http://www.postgresql.org/message-id/3e887762.5b68f...@yahoo.com Oops. I saw that message

Re: [HACKERS] Why data of timestamptz does not store value of timezone passed to it?

On 08/28/2014 01:51 AM, rohtodeveloper wrote: Hi,all I have a question about data type timestamp with time zone. Why data of timestamptz does not store value of timezone passed to it? Considering the following example. postgres=# select '2014-08-28 14:30:30.423602+02'::timestamp with time

Re: [HACKERS] Hokey wrong versions of libpq in apt.postgresql.org

On 08/07/2014 04:30 PM, Joshua D. Drake wrote: Hello, I know this has been brought up before: http://www.postgresql.org/message-id/20140724080902.ga28...@msg.df7cb.de For reference, libpq and packaging issues discussed here as well:

Re: [HACKERS] I thought we were changing the name of recvlogical?

On 05/20/2014 08:48 AM, Josh Berkus wrote: I can't find the thread now, but I'm pretty sure that we decided to change the name of pg_recvlogical, because its inconsistent with other client utils? No? This thread, perhaps??

Re: [HACKERS] Patch: iff - if

On 04/15/2014 05:36 PM, Andrew Dunstan wrote: On 04/15/2014 06:26 PM, Thom Brown wrote: On 15 April 2014 23:19, Andreas 'ads' Scherbaum adsm...@wars-nicht.de wrote: Hi, stumbled over a number of iff in the source where if is meant - not sure what the real story behind this is, but attached

[HACKERS] Documentation patch for to_date and to_timestamp

The attached patch is in response to ongoing mailing-list questions regarding perceived weirdness in to_timestamp and to_date. The patch modifies doc/src/sgml/func.sgml to add (see usage notes) in the description column for to_date and to_timestamp in the Formatting Functions table and adds

[HACKERS] Documentation patch for date/time formatting functions

Due to a variety of messages over time regarding perceived weirdness in to_timestamp and to_date, this patch adds (see notes) in the description column for to_date and to_timestamp in the Formatting Functions table and adds the following text to the opening of the usage notes for date/time

Re: [HACKERS] Personal note: taking some vacation time in Sep/Oct

On 08/19/2013 11:55 PM, Gavin Flower wrote: On 20/08/13 15:26, Tom Lane wrote: I will be taking a long (and long-overdue) vacation... but, But, BUT, you're not human - you can't possibly take leave, the sky will fall all manners of divers calamities will come to pass!!! As if on cue:

Re: [HACKERS] Deprecating RULES

On 10/17/2012 04:25 PM, Tom Lane wrote: ...Now having said that, I would definitely like to see rules in their current form go away eventually. But not without a substitute. Triggers are not a complete replacement, and no amount of wishful thinking makes them so. ... Perhaps it would be more

Re: [HACKERS] 9.2 bug? variable not found in subplan target list

On 09/12/2012 07:36 AM, Louis-David Mitterrand wrote: See test case at: http://titus.apartia.fr/stuff/pg_92_error_sql.txt Works fine on 9.1 I cannot absolutely say it is a bug as I haven't yet reviewed the relevant release notes but I can confirm that I also see your test-case working on

Re: [HACKERS] pgstat wait timeout

On 12/28/2011 05:05 AM, Alvaro Herrera wrote: Excerpts from Steve Crawford's message of mar dic 27 22:51:06 -0300 2011: I have a system (9.0.4 on Ubuntu Server 10.04 LTS x86_64) that is currently in test/dev mode. I'm currently seeing the following messages occurring every few seconds: ... Dec

Re: [HACKERS] pgstat wait timeout

On 12/28/2011 09:34 AM, Alvaro Herrera wrote: Excerpts from Steve Crawford's message of mié dic 28 13:24:37 -0300 2011: On 12/28/2011 05:05 AM, Alvaro Herrera wrote: Excerpts from Steve Crawford's message of mar dic 27 22:51:06 -0300 2011: I have a system (9.0.4 on Ubuntu Server 10.04 LTS

[HACKERS] pgstat wait timeout

I have a system (9.0.4 on Ubuntu Server 10.04 LTS x86_64) that is currently in test/dev mode. I'm currently seeing the following messages occurring every few seconds: ... Dec 27 17:43:22 foo postgres[23693]: [6-1] : WARNING: pgstat wait timeout Dec 27 17:43:27 foo postgres[27324]: [71400-1] :

Re: [HACKERS] pg_upgrade - add config directory setting

On 09/29/2011 08:20 AM, Bruce Momjian wrote: ... 1 document the limitation and require users to use symlinks 2 add a --old/new-configdir parameter to pg_upgrade 3 have pg_upgrade find the real data dir by starting the server 4 add a flag to some tool to return the real data dir, and

Re: [HACKERS] pg_upgrade - add config directory setting

On 09/28/2011 12:49 AM, Peter Eisentraut wrote: On tis, 2011-09-27 at 16:13 -0700, Steve Crawford wrote: It would perhaps be useful to add optional --old-confdir and --new-confdir parameters to pg_upgrade. If these parameters are absent then pg_upgrade would work as it does now and assume

[HACKERS] pg_upgrade - add config directory setting

It would perhaps be useful to add optional --old-confdir and --new-confdir parameters to pg_upgrade. If these parameters are absent then pg_upgrade would work as it does now and assume that the config files are in the datadir. The reason for this suggestion is that packages for Ubuntu (and I

Re: [HACKERS] generate_series() Interpretation

On 06/27/2011 10:49 AM, David E. Wheeler wrote: Hackers, I'm curious about behavior such as this: bric=# select generate_series('2011-05-31'::timestamp , '2012-04-01'::timestamp, '1 month'); generate_series - 2011-05-31 00:00:00 2011-06-30 00:00:00 2011-07-30

Re: [HACKERS] generate_series() Interpretation

On 06/27/2011 10:56 AM, David E. Wheeler wrote: On Jun 27, 2011, at 10:54 AM, Steve Crawford wrote: That's just how intervals that represent varying periods of time work. You would need to write your own. But a series of end-of-month dates is pretty easy: select generate_series('2011-06-01

Re: [HACKERS] generate_series() Interpretation

Yeah, which is why I said it was subject to interpretation. Of course there's no way to tell generate_series() which to use, which is what I figured. Fortunately PostgreSQL uses the same interpretation for '1 month' when used in generate_series that it does everywhere else - to do otherwise

Re: [HACKERS] storing TZ along timestamps

On 06/01/2011 05:18 PM, Alvaro Herrera wrote: Excerpts from Jeff Davis's message of mié jun 01 19:57:40 -0400 2011: On Fri, 2011-05-27 at 16:43 -0400, Alvaro Herrera wrote: Hi, One of our customers is interested in being able to store original timezone along with a certain timestamp. I

Re: [HACKERS] storing TZ along timestamps

On 05/28/2011 02:58 PM, Peter Eisentraut wrote: On fre, 2011-05-27 at 16:57 -0700, Steve Crawford wrote: And the second case is already well handled. In fact calendaring is a great example. I enter the time for the teleconference and PG nicely uses my default timezone to store the point-in-time

Re: [HACKERS] storing TZ along timestamps

On 05/27/2011 01:43 PM, Alvaro Herrera wrote: Hi, One of our customers is interested in being able to store original timezone along with a certain timestamp. I am very interested in the use-case for this (in part as I'm working on a PG related time talk). My experience thus far is that people

Re: [HACKERS] storing TZ along timestamps

On 05/27/2011 04:29 PM, Greg Stark wrote: On Fri, May 27, 2011 at 4:13 PM, Steve Crawford scrawf...@pinpointresearch.com wrote: I am very interested in the use-case for this (in part as I'm working on a PG related time talk). My experience thus far is that people who want this do not fully

Re: [HACKERS] [GENERAL] Date conversion using day of week

On 03/31/2011 08:00 AM, Adrian Klaver wrote: On Wednesday, March 30, 2011 8:39:25 pm Brendan Jurd wrote: On 31 March 2011 03:15, Steve Crawfordscrawf...@pinpointresearch.com wrote: On 03/29/2011 04:24 PM, Adrian Klaver wrote: ... Well the strange part is only fails for SUN:...

Re: [HACKERS] [GENERAL] Date conversion using day of week

On 03/31/2011 10:51 AM, Brendan Jurd wrote: I agree with your summary of the ISO standards. Unfortunately, to_date and its cohorts are not targeting ISO. They are targeting quasi-compatibility with some Oracle functions of the same name, I suppose to make life easier for folks who are

Re: [HACKERS] [GENERAL] Date conversion using day of week

On 03/29/2011 04:24 PM, Adrian Klaver wrote: ... Well the strange part is only fails for SUN:... test(5432)aklaver=select to_date('2011-13-SUN', 'IYYY-IW-DY'); to_date 2011-03-28 ... You specified Sunday as the day but the date returned is a Monday. I would categorize that as

Re: [HACKERS] Determining period between 2 dates

On 02/16/2011 09:07 AM, Marti Raudsepp wrote: On Wed, Feb 16, 2011 at 18:03, Thom Brownt...@linux.com wrote: For the number of fortnights, that becomes: select extract(epoch from now() - '2010-01-01 11:45:13'::timestamp)/60/60/24/14; You'd think with PostgreSQL having such a rich type

Re: [HACKERS] unlogged tables

On 11/17/2010 12:48 PM, Andrew Dunstan wrote: Maybe VOLATILE for UNSYNCED? Not sure about UNLOGGED. UNSAFE and EXTREMELY_UNSAFE?? :) Cheers, Steve -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription:

Re: [HACKERS] unlogged tables

On 11/17/2010 11:44 AM, Tom Lane wrote: ...because a backend crash has to be assumed to have corrupted unlogged tables... So in a typical use-case, say storing session data on a web-site, one crashed backend could wreck sessions for some or all of the site? Is there a mechanism in the

Re: [HACKERS] what is good solution for support NULL inside string_to_array function?

Tom Lane wrote: Josh Berkus j...@agliodbs.com writes: quietly removing NULL is maybe good for compatibility but is wrong for functionality. I agree. I wasn't aware of this little misfeature. Default display for NULL should be a zero-length string. That's just

Re: [HACKERS] Anyone know if Alvaro is OK?

Marc G. Fournier wrote: Is there a higher then normal amount of earthquakes happening recently? haiti, japan just had one for 6.9, there was apparently one in illinos a few weeks back, one on the Russia/China/N.Korean border and now Chile? Random events come in bunches - something I

Re: [HACKERS] array_to_string bug?

Tom Lane wrote: David Fetter da...@fetter.org writes: The next one is just plain unexpected. array_to_string ignores null elements. What do you think it should do with them? regards, tom lane This seems somewhat related to the long-running discussion from

Re: [HACKERS] EOL for 7.4?

Many people still run [7.4], so why make them move? Many people still run 7.3... We made them move.. A nitpick. Nobody made anyone move. PHP 4 was EOL some time ago but is still in widespread use. We still see occasional postings regarding 7.3 and sometimes even earlier. The software

Re: [HACKERS] EOL for 7.4?

Josh Berkus wrote: ...The main reason I'm in favor of this is that we have a lot of users using 7.4 out of inertia, and they need a message that 7.4 is not supported to get them to upgrade. I'm not entirely sure that inertia is the culprit. From what I've seen, since 7.4 is a good, stable

Re: [HACKERS] Maintenance Policy?

Tom Lane wrote: Andrew Dunstan and...@dunslane.net writes: I think we can avoid most of these problems by making a best effort policy rather than a hard promise. But it can be moderately specific about what we will make best efforts towards. I agree that anyone who wants a hard promise

Re: [HACKERS] [GENERAL] string_to_array with empty input

Did I miss the exciting conclusion or did this drift silently off radar? I seem to recall three options: 1. Leave as is. Arguments: least effort, no backward compatibility issues, since array_to_string evaluate both an array with single empty string and an array with no elements to an empty

Re: [HACKERS] [GENERAL] string_to_array with empty input

Tom Lane wrote: I'm starting to vacillate again. It's clear that for the purposes of string_to_array, an empty input string is fundamentally ambiguous: it could mean a list of no things, or a list of one empty thing. Agreed. Of the two, a list of one empty thing makes string_to_array

Re: [HACKERS] What's going on with pgfoundry?

Kris Jurka wrote: On Wed, 26 Nov 2008, Dave Page wrote: It's the same IP address - but try port 35 for ssh. Marc changed it (temporarily) due to a vast number of malicious connection attempts. Why wasn't this change communicated to anyone, not even gforge-admins? How temporary is

Re: [HACKERS] What's going on with pgfoundry?

David Fetter wrote: We should move to a port-knocking http://dotancohen.com/howto/portknocking.html or other modern strategy if we're going to move at all. Yeah, but telling my firewall to move port 22 inside to port outside took less time than writing this email. Inside the firewall

Re: [HACKERS] What's going on with pgfoundry?

Joshua D. Drake wrote: On Wed, 2008-11-26 at 18:06 -0400, Marc G. Fournier wrote: Since were chatting :P. My vote would be to move everything back to port 22 and force key based auth only. How does that work? Does that kill the script kiddies in their tracks? I'm guessing so,

Re: [HACKERS] Monitoring postgres

Kellyton Campos Feitosa - GYN wrote: Dears, I need monitor a postgres database, but I don’t know which tool to use. The tool need perform the below actions 1. show transactions pendents 2. show the statistics per session actives 3. show the statistics per database 4. show metrics

Re: [HACKERS] Do we really need a 7.4.22 release now?

Tom Lane wrote: Yeah. What this is about is how long the *community* supports 7.4... Perhaps the discussion should be more global (and ultimately save time on having this discussion again in the future). Decide on the policy, make official and make it obvious. The time I usually hear

OT: Re: [HACKERS] A new take on the foot-gun meme

Gregory Stark wrote: Shane Ambler [EMAIL PROTECTED] writes: Robert Treat wrote: So is that a golf club gun? Careful what you wish for http://www.totallyabsurd.com/12gaugegolfclub.htm I reckon they watched Caddyshack (I think that was the one) and thought they

Re: [HACKERS] [GENERAL] SHA1 on postgres 8.3

David Fetter wrote: On Wed, Apr 02, 2008 at 12:27:15PM -0400, Tom Lane wrote: David Fetter [EMAIL PROTECTED] writes: Just exactly which encryption legislation are we talking about here? I know there was some fuss about this issue back in the early 1990s, but that was many, many

Re: [HACKERS] TRUNCATE TABLE with IDENTITY

Simon Riggs wrote: RESTART IDENTITY will reset the SERIAL sequences back to the original start value. Assuming this feature were to be added In cases where the same sequence has been used across multiple tables, what will be the appropriate response when a user attempts to TRUNCATE

Re: [HACKERS] CVS repository rsync

Magnus Hagander wrote: I've set up my laptop to sync down the full cvs repository using rsync (remember - windows = no cvsup). This works well, except every now and then (not every time, but definitly often enough to bother me) it resyncs the entire repository, and not just the files that have

[HACKERS] Feature request (was psql: absolutes and toggles)

desires. Cheers, Steve Peter Eisentraut wrote: Steve Crawford wrote: We create psql scripts that can be used at various times by various users. I have been unable to find how to absolutely set various options (timing, expanded, etc.) rather than toggle them. The --no-psqlrc option provides

Re: [HACKERS] The Contrib Roundup (long)

On Friday 10 June 2005 10:54 am, Kaare Rasmussen wrote: actually I think part of the point of this was to give a command line version of the reindex command, like we have for vaccum. If that still matters, then it should probably stay. Actually it should probably be converted to C and

Re: [HACKERS] [ADMIN] Excessive growth of pg_attribute and other system tables

On Thursday 31 March 2005 12:06 pm, Tom Lane wrote: I wrote: The light just went on ... system catalog updates don't generate statistics reports. Hence, autovacuum doesn't know any work is needed. The above claim is too strong --- they do normally generate stats updates. However, in a

Re: [HACKERS] Bug 1500

So this bug actually brings the issue of interval to_char() formatting. Opinions? In digging around I discovered that it appears a decision was made to remove to_char(interval) at the 8.1 release but I've been unable to find the replacement for this functionality. This alarms me. Given the

Re: [HACKERS] CVS should die (was: Possible make_oidjoins_check ...)

This doesn't really answer the question of what tool Postgres might change to, but it seems that Subversion is a good tool one should consider. And by golly, CVS is bad. Just consider the cons having to forbid renames in all but the most necessary cases it just invites cruft into any

Re: [HACKERS] Time off

Its also an unusual replication scheme in that, more often than not, the slaves control the masters. As the slave of a replica with an 86 day 16 hour uptime I've also discovered that the new I/O functions take some adjustment as does working around the lack of sleep(3). Cheers, Steve

Re: [HACKERS] Email data type

On Monday 17 May 2004 8:45 am, Steve Atkins wrote: Also, [EMAIL PROTECTED] is a syntactically valid email address, in the .13 TLD. It does not deliver to 10.11.12.13, or anywhere else, as of today, unless the MTA or local recursive resolver is broken (a common case). [EMAIL PROTECTED] is a

Re: [HACKERS] Log rotation

On Sunday 14 March 2004 1:00 pm, Tom Lane wrote: ... So it seems fairly likely that the fsync-by-default business is indeed a Linux-ism not shared by other Unixen. Excerpt from the Postfix 2.0.8 README_FILES/LINUX_README file in case it proves interesting: - LINUX syslogd uses

Re: [HACKERS] Sigh, 7.3.6 rewrap not right

On Thursday 04 March 2004 7:28 pm, Tom Lane wrote: Lamar Owen [EMAIL PROTECTED] writes: Please, don't call it 7.3.6. Streamlining releases is terrible. 7.3.7 or 7.3.6.1 or SOMETHING other than 7.3.6, and just let 7.3.6 be a brown paper bag release (like 6.4.1 was). There were no

[HACKERS] psql copy help

The psql help for copy (version=7.3.2 and several others) appears incorrect (or perhaps the command parser is at fault - in any case the help doesn't match reality): steve=# \h copy Command: COPY Description: copy data between files and tables Syntax: COPY table [ ( column [, ...] ) ]

[HACKERS] pg_conf idea (was Re: [GENERAL] Postgres performance comments from a MySQL user)

On Wednesday 11 June 2003 2:37 pm, Matthew Nuzum wrote: The problem with this is that in troubleshooting there's no frame of reference. Having a stock config file, or stock config file options allows a person to write to the list and say, hey, I'm using medium.conf and I have x ram... The

Re: [HACKERS] Error message style guide

One thing that would be great from a user's perspective (and which might reduce the volume of support questions as well) is to uniquely number all errors as in: Error 1036: the foo could not faz the fleep The advantages of this include: Ease of documentation: a manual could containg a section

Re: [HACKERS] location of the configuration files

On Friday 14 February 2003 6:07 am, Martin Coxall wrote: On Thu, 2003-02-13 at 20:28, Steve Crawford wrote: I don't see why we can't keep everyone happy and let the users choose the setup they want. To wit, make the following, probably simple, changes: 1) Have postgresql default to using

Re: [HACKERS] location of the configuration files

I don't see why we can't keep everyone happy and let the users choose the setup they want. To wit, make the following, probably simple, changes: 1) Have postgresql default to using /etc/postgresql.conf 2) Add a setting in postgresql.conf specifying the data directory 3) Change the meaning of -D

Re: Changing the default configuration (was Re: [pgsql-advocacy] [HACKERS] PostgreSQL Benchmarks)

A quick-'n'-dirty first step would be more comments in postgresql.conf. Most of the lines are commented out which would imply use the default but the default is not shown. (I realize this has the difficulty of defaults that change depending upon how PostgreSQL was configured/compiled but

Re: [HACKERS] PGP signing releases

Having just started working with GPG I shouldn't be considered an expert but it seems to me that each core developer should create a key and should cross-sign each others' keys to form a web of trust to verify the authenticity of those signatures. In any case, I think that if security-related

Re: [HACKERS] Linux.conf.au 2003 Report

What about cases where I only want one or the other? Would a simple method exist to limit input to v4 or v6 only? Also, what are the implications to functions such as network_sub, network_cmp, etc. when given mixed v4/v6 inputs as could easily happen if the two are freely mixed in the same

Re: [HACKERS] [GENERAL] RC2 Packaged in Preparation for a Wednesday Release ...

SuSE 7..3 (2.4.10-4GB) Compiles and passes regression fine: All 89 tests passed. Installing to dev server next. Cheers, Steve On Monday 25 November 2002 8:19 am, you wrote: Morning all ... On Sunday this weekend, we packaged up PostgreSQL v7.3rc2 for testing ... this release, if all