th similar structure that all exhibit the same
behavior) and yes I've done ANALYZE and VACUUM and the
behavior doesn't change.
--
Bill Moran
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
s or instabilities in PostgreSQL 9.6.
Wow ... this may be the most unusual survey I've seen in a while.
--
Bill Moran
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
; error. The problem is that the second error
masks the first one, hiding the real cause of the connection
failure, and causing a lot of confusion.
If we could keep both errors and report them both, I feel like
it would be an improvement to our client library behavior.
--
Bill Moran
--
Se
code, please contact me so we don't double
up on the work.
--
Bill Moran
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
isable unique indexes. Arguably,
unique indexes are actually an implementation detail of unique
constraints. Disabling a performance-based index doesn't cause data
corruption, whereas disabling an index created as part of unique
constraint can allow invalid data into the table.
Just my $.02 ..
localhost.
On posix systems, it's cusomary to put multiple names in the hosts file,
localhost included. I expect that Windows is the same, but I haven't used
it in so long that I can't be sure.
--
Bill Moran
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.
On Wed, 4 Nov 2015 13:07:09 +0800
Craig Ringer wrote:
> On 4 November 2015 at 10:58, Bill Moran wrote:
> > On Tue, 3 Nov 2015 18:34:39 -0800
> > Jeff Janes wrote:
> >
> >> On Tue, Nov 3, 2015 at 5:21 PM, Craig Ringer wrote:
> >> > On 3
On Tue, 3 Nov 2015 18:34:39 -0800
Jeff Janes wrote:
> On Tue, Nov 3, 2015 at 5:21 PM, Craig Ringer wrote:
> > On 3 November 2015 at 23:04, Bill Moran wrote:
> >>
> >> Looking for feedback to see if anyone sees any issues or has any
> >> suggestions on what
an
the patch for anyone: https://github.com/williammoran/postgres
--
Bill Moran
diff -r --exclude=.git --exclude=src/test --exclude=README postgres_head/doc/src/sgml/config.sgml postgres_new/doc/src/sgml/config.sgml
6708a6709,6773
>
> TOAST
>
>
&
On Wed, 28 Oct 2015 16:58:30 -0400
Peter Eisentraut wrote:
> On 10/28/15 10:27 AM, Bill Moran wrote:
> > See subject. Aside from them being divvied up by datatype, they seem
> > to be ordered randomly. Since I'm putting together a patch that will
> > add some GUCs, do
See subject. Aside from them being divvied up by datatype, they seem
to be ordered randomly. Since I'm putting together a patch that will
add some GUCs, do I just add them to the end of the list?
--
Bill Moran
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
o the plural, where possible?
>
> So
>
> "any user can make such a change for his session."
>
> becomes
>
> "Users can make such a change for their individual sessions"
>
> or similar?
+1
As an American/native English speaker, I find the
; David.
>
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
--
Bill Moran
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sat, 25 Jul 2015 16:06:28 -0400
Tom Lane wrote:
> Bill Moran writes:
> > On Sat, 25 Jul 2015 11:39:15 -0700
> > Josh Berkus wrote:
> >> Nope. In fact, even the one which was 90% complete (replacing zlib with
> >> lz4) completely dropped off the radar
On Sat, 25 Jul 2015 11:39:15 -0700
Josh Berkus wrote:
> On 07/25/2015 07:05 AM, Bill Moran wrote:
> >
> > If not, I'm going to make a little personal project of them for myself
> > (targeting 9.6).
> >
>
> Nope. In fact, even the one which was 9
If not, I'm going to make a little personal project of them for myself
(targeting 9.6).
--
Bill Moran
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
In response to Jeff Janes :
> On Fri, Dec 17, 2010 at 12:16 PM, Bill Moran wrote:
> > In response to Tom Lane :
> >
> >> Josh Berkus writes:
> >> > postgres=# select '1e+01'::Integer
> >> > postgres-# ;
> >> > ERROR: invalid
rguing on Tom's
side, that we should not support such a conversion ... actually, I'm
not sure what side of this I'm on right now, I'm just providing
evidence ...
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
s in exponential
notation when the numbers are very large (PHP is the only example that
comes to mind, but it's a pretty common language) which may cause numbers
formatted thusly to be included in queries without the programmers prior
realization.
--
Bill Moran
http://www.potentialtech.com
;t think this change is nearly as severe as the cast
change in 8.3, and I don't feel it warrants the same eggshell walking.
When the decision is made to remove the standard_conforming_string
config option altogether ... that'll be a different story!
--
Bill Moran
http://www.potentialtec
be
left in for a few more releases until newer versions of FreeBSD are the
standard.
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
bout plataforms (Windows) that don't have ulimit?
I have a hard time believing that Windows doesn't have a ulimit equivalent.
I don't want to degrade this thread into MS-bashing, but if that were the
case, it would make Windows a pretty crippled OS.
--
Bill Moran
http://www.pote
rs dots
I think you've missed the point. If a loadable module is used, then
it can do anything the DBAs need it to. You can write your own module
if you're not happy with those provided. At that point, arguing about
what makes a good password is pretty irrelevant. Note the parag
ere's the party? ;)
In any event, happy birthday.
--
Bill Moran
http://www.potentialtech.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
a subselect (which is often not enough because then you
> > can't use outer joins).
>
> So the problem is that our DELETE ... USING does not allow ANSI join
> syntax? Can that be added?
I suspect that the reason MySQL has this syntax is because for a long time
they
data
for other roles and sign data, thus allowing some really powerful data
protection schemes.
Just coming up with a methodology for this is non-trivial, though.
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
t; fundamentally flawed?
It seems to me that you're duplicating the functionality that is already
possible by using groups. i.e. grant the permissions to the group and
add users to the group as appropriate.
--
Bill Moran
http://www.potentialtech.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
In response to to...@tuxteam.de:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Apr 23, 2009 at 01:31:39PM -0700, Marc Munro wrote:
>
> [...]
>
> > In principle it could be used in the way that Bill Moran suggests though
> > I have never
In response to to...@tuxteam.de:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Apr 23, 2009 at 10:38:55AM -0400, Bill Moran wrote:
> [...]
>
> > It's possible that this could be accomplished by something like Veil,
> > or the built-in implemen
In response to Tom Lane :
> Bill Moran writes:
> > In response to Tom Lane :
> >> We should presumably let the encoding be changed when cloning
> >> from template0, and probably it's reasonable to trust the user
> >> if either source or destination DB e
template can't be converted to the
desired encoding. I mean, I can always alter template1 by inserting
non-utf8 data, and then try to use it to create a utf8 encoded
database ...
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
In response to to...@tuxteam.de:
>
> On Thu, Apr 23, 2009 at 10:38:55AM -0400, Bill Moran wrote:
>
> [...]
>
> > It's possible that this could be accomplished by something like Veil,
>
> Veil? Care to share an URL?
Google knows :)
http://veil.projects.p
theft,
etc (really, just about every attack vector aside from password brute
forcing and social engineering ... and those will require other
methods of protection anyway.)
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
now of lots of code that I've written that accesses those
catalogs. I can't speak for other people.
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
suspect are causing unwarranted temp files on a production server,
I can enable it on a per-connection basis to track down the problem and
work on a specific query, on production systems, without too much
disruption of the rest of the work that's going on:
set log_temp_files = 0;
se
d this devilish master plan that - values would
be less than and positive values greater than, then I decided I was
being stupid.
So, that's my input. But, at this point I'm not entirely sure what the
best approach is.
--
Bill Moran
Collaborative Fusion Inc.
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
In response to Tom Lane <[EMAIL PROTECTED]>:
> Bill Moran <[EMAIL PROTECTED]> writes:
> > Andrew Dunstan <[EMAIL PROTECTED]> wrote:
> >>> Might be more robust to say
> >>> if (trace_temp_files >= 0)
>
> > I specified in the GUC confi
In response to "Simon Riggs" <[EMAIL PROTECTED]>:
> On Tue, 2007-01-02 at 18:20 -0500, Tom Lane wrote:
> > Bill Moran <[EMAIL PROTECTED]> writes:
> > > In response to Alvaro Herrera <[EMAIL PROTECTED]>:
> > >> Please change things to sav
.
Am I hitting something such as file sparseness? Is this entire endeavour
doomed from the start? Or am I just making some sort of dumb mistake?
Any pointers are welcome.
--
Bill Moran
Collaborative Fusion Inc.
diff -r src.orig/backend/storage/file/fd.c src/backend/storage/file/fd.c
52a53
&g
In response to Andrew Dunstan <[EMAIL PROTECTED]>:
> Bill Moran wrote:
> > I see the above-mentioned files in src/backend/utils/misc. A diff shows
> > the following:
> >
> > $ diff postgresql.conf.sample.orig postgresql.conf.sample
> > 223a22
postgresql.conf.sample.orig?
I'm adding a GUC variable to submit a patch to allow tracing temp file
usage. Do I need to add it to both?
--
Bill Moran
Collaborative Fusion Inc.
---(end of broadcast)---
TIP 6: explain analyze is your friend
Bruce Momjian wrote:
Bill Moran wrote:
Hey all,
I hope this isn't off-topic or inapropriate to this list ...
I'm not familiar with the PostgreSQL patch-submittal/development cycle.
I recently submitted a patch regarding \copy syntax in psql, and I'd
like to keep an eye on it to s
omitter?
Direct suggestions, or links to information would be equally welcome.
Thanks.
--
Bill Moran
Potential Technologies
http://www.potentialtech.com
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
43 matches
Mail list logo