hat setting a new default to a potentially destructive setting is
problematic. Still, I do believe that the current state of affairs is
painful and problematic and this is a problem worth solving.
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt."—Kurt Vonnegut
.
If folks are comfortable with this change, I'll provide a patch for the
current commitfest.
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt."—Kurt Vonnegut
via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt."—Kurt Vonnegut
have no
> quotations marks around them).
>
> Regards,
> Sven
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt."—Kurt Vonnegut
progress here, users continue to get
bad advice about using the existing MONEY type such as here:
http://stackoverflow.com/questions/15726535/postgresql-which-datatype-should-be-used-for-currency
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt."—Kurt Vonnegut
On Mon, Jan 23, 2017 at 4:12 PM, Jim Nasby wrote:
> On 1/23/17 3:45 PM, Peter van Hardenberg wrote:
>
>> A new currency type would be nice, and if kept small in scope, might be
>> manageable.
>>
>
> I'd be rather nervous about this. My impression of communit
ack
in the day... That's still a gap in community Postgres.
On Mon, Jan 16, 2017 at 6:43 PM, Jim Nasby wrote:
> On 1/13/17 3:09 PM, Peter van Hardenberg wrote:
>
>> A new data type, and/or a new index type could both be nicely scoped
>> bits of work.
>>
>
> Did you
>
>>
>> --
>> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-hackers
>>
>
>
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt."—Kurt Vonnegut
On Wed, Oct 19, 2016 at 3:08 PM, Robert Haas wrote:
> On Mon, Oct 26, 2015 at 4:25 PM, Peter Eisentraut wrote:
> > On 10/14/15 6:41 AM, Victor Wagner wrote:
> All in all, I'm still feeling pretty good about trying to support the
> same syntax that our JDBC driver already does. It's certainly no
me: 176460001.200 ms (2 01:01:00.001)
> Time: 216720001.200 ms (2 12:12:00.001)
> Time: 8816460001.200 ms (102 01:01:00.001)
> Time: 8856720001.200 ms (102 12:12:00.001)
>
> Barring objections I'll commit this soon.
>
> regards, tom lane
>
Some kind of units on the parenthetical format would be helpful. Glancing
at several of these values it takes me a couple of seconds to decide what
I'm reading.
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt."—Kurt Vonnegut
On Tue, Jul 26, 2016 at 6:15 PM, Peter Eisentraut <
peter.eisentr...@2ndquadrant.com> wrote:
> On 7/26/16 6:14 PM, Vik Fearing wrote:
> > As mentioned elsewhere in the thread, you can just do WHERE true to get
> > around it, so why on Earth have it PGC_SUSET?
>
> I'm not sure whether it's supposed
json array and
> attempt to convert it directly into a PostgreSQL array. Just a conversion
> is not always going to succeed though the capability seems worthwhile if as
> yet unasked for. The each->convert->array_agg pattern works but is likely
> inefficient for homogeneous json array cases.
>
> David J.
>
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt."—Kurt Vonnegut
I'll look into it, thanks for the explanation.
On Mon, May 23, 2016 at 1:37 PM, Tom Lane wrote:
> Peter van Hardenberg writes:
> > Great question, Marko. If you can point me towards an example I'll take a
> > look, but I'll proceed with the current understandi
Great question, Marko. If you can point me towards an example I'll take a
look, but I'll proceed with the current understanding and suggestions and
see what people have to say.
On Mon, May 23, 2016 at 10:47 AM, Marko Tiikkaja wrote:
> On 2016-05-23 18:55, Peter van Hardenberg
or suggestions?
-p
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt."—Kurt Vonnegut
I plan
> to commit this tomorrow.
>
>
No objections here. Thanks Tom and everyone else for setting this straight.
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut
pared statement';
execute sz1;
select 'selecting from z1 to prove it exists';
select * from z1;
On Mon, Jan 21, 2013 at 10:45 PM, Peter van Hardenberg wrote:
> Hm - I'm still able to recreate the test the user's running using
> pg_dump/pg_restore. I'm still
t there's some other critical piece of information he
> left out. I don't plan to speculate about causes without a concrete
> test case.
>
> regards, tom lane
>
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut
nately) possess. A better solution might be to
attempt to re-prepare the statement before throwing an error.
-pvh
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut
On Fri, Nov 2, 2012 at 11:16 AM, Peter Eisentraut wrote:
>
> Did the inserted row also arrive at the standby?
>
No, as there was no standby.
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut
ml=> rollback;
NOTICE: there is no transaction in progress
ROLLBACK
d5r5fdj6u5ieml=>
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut
esults :-(
>
> As for GNU readline, I suspect you weren't actually testing it.
> Note that the thing called /usr/lib/libreadline.dylib is not GNU
> readline, it's only a symlink to libedit.
>
I am indeed running Lion. Thanks for helping me track down the cause.
--
Peter van
On Thu, Feb 23, 2012 at 4:15 PM, Tom Lane wrote:
>> Here's a reliable reproduction on my OS X laptop.
>
> OS X? Are you using GNU readline, or Apple's libedit?
>
I reproduced it with both, but if that news is surprising to you, I
can certainly re-test.
--
Peter van
oh hai ./share
pvh=# \i
I don't see this regression with the 9.1 client I have here, so I
suspect it has something to do with whatever patch introduced the
relative paths by default.
-p
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -
no security concerns with giving users every ability to
execute code as the cluster owner's UNIX user. On our service we do
not restrict our users access to superuser out of spite, but to reduce
the available surface area for self-destruction.
--
Peter van Hardenberg
San Francisco, Californ
On Mon, Dec 12, 2011 at 9:25 PM, Peter Eisentraut wrote:
> On mån, 2011-12-12 at 16:51 -0800, Peter van Hardenberg wrote:
> You don't need a new PL to do that. The existing PLs can also parse
> JSON. So that's not nearly enough of a reason to consider adding this
> new PL.
On Mon, Dec 12, 2011 at 5:05 PM, David E. Wheeler wrote:
> On Dec 12, 2011, at 3:55 PM, Peter van Hardenberg wrote:
>> only a nearly insurmountable mailing list thread
>> prevents it.
>
> What happened to SexQL?
>
Case in point.
--
Peter van Hardenberg
San Francisco, Ca
ts.com
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
are, but in the spirit of full
disclosure, and depending on how you count, we currently have
somewhere between 250,000 and 500,000 URLs which begin with
postgres:// in our care.
--
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut
--
S
s a serious operational concern for me and my team and
I will be personally dealing with fires caused by this for years to come
regardless of the outcome of this thread.
Best,
-pvh
--
Peter van Hardenberg
Department of Data
Heroku
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut
users to specify the versions of extensions
that they need in some kind of a control file or in a database migration
script such that they can then install those extensions on various new
systems in a reliable and reproducible way.
David, if you do what you propose, haven't I already lost?
31 matches
Mail list logo
