we dramatically increase the pool of people
with checksums enabled.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201701211522
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B9
% for nothing.
It is not for nothing, it is for increasing reliability by detecting
(and pinpointing!) corruption as early as possible.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201701211513
http://biglumber.com/
orting effort to any language would be immense.
C++ would be the least painful option, probably.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201701080905
http://biglumber.com/x/web?pk=2529DF6AB8F7940
is issue was raised on July 25th, and the OP has
gone out of his way to present the case and provide patches. It's hardly
fair to discard it now.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 2016080716
2.0 because of cool feature X and reason Y"
we would get the rare message like this:
"We don't really have much for this release, maybe it should just be 11.1?"
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.
te it, or even ensure they
are machine-parseable, but I would like to see a few fields encouraged.
I think it also helps the committers to not forget some important
things, the way the free-form text can.
tl;dr be like Alvaro, please
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corpor
/postgres_all_versions.html#version_9.4.5
which leads to:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5289
It's also possible the wrong CVE was entered, but I don't see
one that seems to pertain to the issue described (and
CVE-2015-5288, -3166, -3167, -0243, -0244 are in the same boat).
--
G
/members files (appears to have wrapped, then truncated)"
http://www.postgresql.org/message-id/flat/20150406192130.2573.22...@wrigleys.postgresql.org#20150406192130.2573.22...@wrigleys.postgresql.org
or:
http://goo.gl/4lKYOC
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://w
ting itself to the driver by
deprecating the ? operator) is not realistically likely to happen.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201505191718
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-B
BC-ish alternatives
like the (very verbose) vendor escape clauses, but settled on the simplicity of
a single backslash in the end. See part of the discussion here:
http://www.nntp.perl.org/group/perl.dbi.users/2014/12/msg37057.html
- --
Greg Sabino Mullane g...@turnstep.com
End Poi
onnector - that's true
for lots of bug fixes and features. This one at least is fairly optional
with many existing workarounds (e.g. use $1, quote things in a different way).
> (It looks like PHP/PDO is another one to add to the list:
> https://bugs.php.net/bug.php?id=62493, it's bee
good one. We still have clients on Postgres 7!
Five years is way too short to replace something that major.
> Agreed a patch would be the first place to start
That, or just running the idea up the flagpole on -general. I'm a fairly
strong -1 at the moment, but will listen to arguments.
. And that's much easier if you're not constrained by 63 chars.
That's silly. We (third-party tools) already have to work around lots
of things constrained by namedatalen.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 2
rivers implement \? as a semi-standard workaround.
See also:
http://blog.endpoint.com/2015/01/dbdpg-escaping-placeholders-with.html
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201505171212
http://biglumber.com/x/web?pk=2529DF6AB8F79407
Just a little thing that's been bugging me. If one side of the
pg_upgrade has checksums and the other does not, give a less
cryptic error message.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
diff --git a/contrib/pg_upgrade/controldata.c b/co
all on one page for easy searching. That would
be awesome.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201502021555
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEARED
es is coming from. The query is: SELECT 'DBD::Pg ping test'
Which also means the inverse is true: simple blank queries
are guaranteed to *not* be coming from DBD::Pg.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 2014123010
we
can assume the backend is bad (for example, PQerrorMessage gives a
"could not receive data from server: Bad file descriptor"). Being that we
cannot do a rollback before calling the PQexec, is this a decent solution?
Can we depend on really serious errors always trumping the expe
up all the patches process. We have git, let's use it
as it was intended.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201412141011
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEG
h client libraries that like
> to issue BEGIN and then go idle until they have something to do.
> Which, for some reason, is a prevalent behavior.
I'm not advocating changing the default behavior, but I would not want
to see bad client libraries used a reason for any change we make. Cl
would be helpful to know what problem
> it is attempting to solve.
Seems like a decent solution to me. The problem it that having to execute
a dummy SQL statement to start a serializable transaction, rather
than simply a BEGIN, is ugly.and error prone. Perhaps their app
assumes
relying on v2 behavior get rewritten, or make the driver smart
enough to handle it automagically the best it can.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201410060710
http://biglumber.com/x/web?pk=2529DF6AB8F79407E
current capabilities around logging and auditing are dismal
No arguments there.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201408271200
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964A
his one was tricky)
* allow future git integration based on subsytems
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201401261211
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964A
different words if I ever end up
> doing a list again.
Please, don't ever do a list again. And yes, "slacker" was an extremely
poor choice of word. This American English speaker certainly has a
hard time viewing it as "affectionate". I think the whole thread would
ha
hould
be much easier and more intuitive. As far as "rewarding" current reviewers,
put the names in the release notes, after each item. Full stop.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201306271636
http://biglumber.com/x/w
e,
> but which time you will have lost interest in the patch anyway.
+1 to all that. Especially the signing up for the commitfest app.
> Of course, Gerrit doesn't actually address most of the issues above, but
> it could be part of a step forward.
More of a step sideways
e
had to do a lot of work to make things usable, despite their having a
non-email-centric workflow already.
Maybe we can identify specific issues with our current app instead?
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201302081106
http://biglumbe
Sure there is a point - emulating some other system. Could be
replication, QA box, disaster recovery, etc. I'd be
cool with a warning, but do not think we should disallow it.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x1496
t for the next four months, if that makes you feel better! :)
Congrats!
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201210271914
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAlCMau4ACgkQvJuQZxSWSshdoQCg6e
st so we can
deprecate rules.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201210112251
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAlB3hx8ACg
t the
same time that logins are working? :)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201210101310
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEG
only care if things are
working all the up to point A or not, where point A is usually
a simple query such as "SELECT 1". Knowing various failure states
as returned by PQping* does not seem to fit into such tools -
any failure needs to be handled manually.
- --
Greg Sabino Mullane g
b, of course.
I'm not convinced of the merit of that plan, but that's an alternative
interpretation that doesn't involve our beloved pgfoundry. :)
Oh, and -1 for putting it in core. Way too early, and not
important enough.
- --
Greg Sabino Mullane g...@turnstep.com
it'd be a lot of work for
> dubious reward, and it would almost certainly generate a pile of
> application compatibility problems.
Okay, but what about a more targeted solution to the original
poster's problem? That seems doable without causing major
breakage elsewhere
- --
G
uses* pg_bench for
its tests already, once could argue a limited test case - but it seems
difficult to design some pg_bench options generic and powerful enough
to handle other cases outside of the one software this change is aimed at.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corpor
this thread asked for.
> 3) use a purposefully slow hashing function like bcrypt.
>
> but I disagree: I don't like any scheme that encourages use of low
> entropy passwords.
Perhaps off-topic, but how to do you figure that?
- --
Greg Sabino Mullane g...@turnstep.com
End
0 of 8192 bytes
LOCATION: mdread, md.c:631
(5 times) Cache lookup failure:
XX000: cache lookup failed for relation 1554847255
LOCATION: has_subclass, plancat.c:921
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpBH51gd5sgI.pgp
Description: PGP signature
in the same place.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpSmpP1G2bZT.pgp
Description: PGP signature
lar case:
STATEMENT: UPDATE mytable SET foobar = 'T' WHERE id IN ($1,$2,$3,$4)
I'll start the wheels rolling for upping the verbosity.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgp1V3duXPAQS.pgp
Description: PGP signature
prod.
No idea if this related to the relatively recent btree errors, but figured
I would get it out there. There is also an even rarer sprinkling of:
ERROR: relation with OID 3924107573 does not exist
but I figured that was probably a variant of the first error.
--
Greg Sabino Mullane g...
l the temp stuff being created and torn down all day, as well as
some Bucardo pg_class updating.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpLQFTbOf8Tw.pgp
Description: PGP signature
am guessing where
the temp tables come from (work_mem is 24MB). I'm not sure I understand
what could be causing both the 'read 0' and btree errors for the
same query - bad blocks on disk for one of the underlying tables?
I'll work next on checking each of the tables the v
On Mon, Jun 04, 2012 at 02:09:44PM -0400, Tom Lane wrote:
> Greg Sabino Mullane writes:
> > We have a 8.3.18 system (yes, the same one from the previous
> > thread, finally upgraded!) that gave us this error yesterday:
>
> > ERROR: index "pg_class_oid_index"
for or can
proactively do? No other system catalog problems have been seen
before it or since.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgp83Kexp6hqX.pgp
Description: PGP signature
ry tables created.
For the record, same here. We do *lots* of DDL (hence the cronjobs
to vac/reindex system catalogs).
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpuQRprn1huB.pgp
Description: PGP signature
On Sat, May 26, 2012 at 01:25:29PM -0400, Tom Lane wrote:
> Greg Sabino Mullane writes:
> > On Sat, May 26, 2012 at 12:17:04PM -0400, Tom Lane wrote:
> >> If you see any block numbers above about 20 then maybe the triggering
> >> condition is a row relocation after
On Sat, May 26, 2012 at 12:17:04PM -0400, Tom Lane wrote:
> If you see any block numbers above about 20 then maybe the triggering
> condition is a row relocation after all.
Highest was 13.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpa6XGTGTE
e
is now 52MB/70MB (the original figures were from yesterday). At any rate,
nowhere near 1/4 shared buffers.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpGtYKGLr70y.pgp
Description: PGP signature
ere may be some other contributing factor that we haven't
> identified yet.
Let me know if you think of anything particular I can test while it is
happening again. I'll try to arrange a (netapp) snapshot the next time
it happens as well (this system is too busy and too large to do an
artup problems appeared.
Let me know if you'd like any of those warnings from the logs.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgp9P2W8oU7Y8.pgp
Description: PGP signature
54846571/pg_internal.init.11803") = -1 ENOENT (No such
file or directory)
12:18:40 open("base/1554846571/pg_internal.init.11803",
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 13
12:18:40 fstat(13, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
12:18:40 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|
y holding
the lock (if any was).
* Did anything in the 8.3 series fix this? I saw nothing relevant in
the release notes for everything up to 8.3.18 (which it will be on soon).
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpwbxRekkZQf.pgp
Description: PGP signature
s mostly answered, and we obviously don't need another
thread, but the answer to the above is "yes".
Release notes are very public, plain text, easy to read, very archived
and searchable. Commit messages might as well be a black hole as far as
visibility to anyone not a developer in
-information.)
+1 to keep things they way they are. If you were significantly invested
in [re]writing the patch, you get a name. Reviewers, I love you dearly,
but you don't belong next to the patch. Group them all at the bottom
if we must have them there.
- --
Greg Sabino
r
>> collaborating on code.
>
> That's about the same amount that I have.
I have no spam at all, despite being a fairly early github adopter.
Wonder what the difference is?
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 2012041
as lots of ideas but
little free time.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201204191031
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
, but anything should be fine as long as we have someone
to take ownership.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201204172131
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAk+OL/0ACgkQvJu
Gerrit and there are definitely
a lot of rough edges in that workflow still.
...
Someone mentioned upthread that github spam was a problem. I'm not sure
I see the issue here - wouldn't mail from them still go through our lists
and out current anti-spam measures anyway?
- --
Greg Sab
hows the committed diffs. Links to a webpage
showing the diff is just not the same.
pgsql-commit-di...@postgresql.org, anyone?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201204121121
http://biglumber.com/x/web?pk=2529DF6AB
s if you don't really care about
sub-second resolutions.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201204091345
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE--
ed a new version but
libxml was being *really* problematic so I abandoned the install, but
I guess it left some pieces around. I will see if I can clean it up.
> BTW, right at the moment you seem to have git issues, too.
Thanks, I will check on that.
- --
Greg Sabino Mullane g...@turnstep.
le: No such file or directory
libtool: install: error: relink `libxml2mod.la' with the
above command before installing it
I don't have time/inclination to track down why the make is failing, but
may have some time to run any Postgres-specific tests, if anyone wishes
me to.
other words, I'll concede int==text, but
really need a strong argument for conceding things like LPAD.
* Your = everyone else, not just M. Haas.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 2
dibly
stupid, see some of the *other* CLIs out there (hi, mysql! :)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201202101157
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEARE
ase issue.
+1 This bit me the other day.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgprM9aFgot2o.pgp
Description: PGP signature
s a pain point people should
pay when going to 9.1, rather than adding some switch now.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgp7jN6DSMohw.pgp
Description: PGP signature
s.
That ship has sailed.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpsMUli41Pnm.pgp
Description: PGP signature
> switch" for cases that cause performance problems.
Eh? It has an off switch: repeatable read.
Thanks for all replying to this thread, it's been very helpful.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpkFVkl3Xl3T.pgp
Description: PGP signature
ern at the moment. Are we
talking insignificant overhead? Minor? Is it measurable? Hard to say without
knowing the number of txns, number of locks, etc.?
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpXfFQOk4fgH.pgp
Description: PGP signature
trip them out after the fact with a little bit of SQL, e.g.
DELETE FROM pg_description WHERE objoid > 5;
(test first, your system may vary and 50000 may not work)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201109
NCTION noreturn()
RETURNS VOID
LANGUAGE plperl
AS $$ while (1) { select (undef,undef,undef,0.1) } $$;
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201109191104
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714
custom format files for each
database. As shell scripts all over the world have been doing for years,
but it would be nice if it was simply built in.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201109012139
http://big
nt database/server,
or to a frozen version of an earlier scan.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201108302203
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iE
g dump file (schema *or* schema+data) that needs
parsing, there is an existing tool:
http://blog.endpoint.com/2010/01/splitting-postgres-pgdump-into-pre-and.html
Once these new flags and the ability to custom format dump pg_dumpall
is done, I'll have very little left to complain abou
y, right?". If so, and if it's potentially blocking a
major new feature, why not now?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201108112140
http://biglumber.com/x/web?pk=25
be done some other way altogether.
Maybe it's time to finally remove the been-deprecated-for-a-while OIDs?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201108111654
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B
well enough: if you are doing something that it matters enough which
tables are shared, you really oughtta know about them anyway.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201106212323
http://b
ql.conf file, especially max_connections (probably one of the
items most closely associated with pg_stat_activity)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201106161132
http://biglumber.com/x/web?pk=2529DF6AB8F7940
itoring shortcomings? Might as well fix as much as we can in one
swoop.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201106151246
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964A
times my fingers
have typed "WHERE current_query <> ''"
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201106142300
http://biglumber.com/x/web?pk=2529
is locked away and cannot
be seen by other processes. I'm sure of this because Bucardo
went through the same questioning some time ago. We basically rewrote
the app a bit to use the on-disk PID files to replace some of the
lost functionality, and sucked up the rest. :)
- --
Greg Sabino M
chance
to step up! :)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201105282322
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAk3hvCgACgkQvJuQZxSWSsi8gwCfQq/2W
formerly resolved as int4 + int4 is now resolved as int2 + int2.
Have I mentioned I'm already a big -1 on the whole idea? :) Yes, this
will be a more subtle problem to diagnose, but I also think it will
affect less code and thus not elicit as much whining. Besides,
I never recommend
8.3 is a sore spot
for me. :)
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201105082230
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAk3HU0IACgkQvJuQZxSWSshp2gCeLzjdXPQ0NkwDzby0f8DzUErz
FUEAoLNkIzJ5jWxVP2Ck3BZ
re* that benefitted from 12 (*okay, a larger handful anyway, it's not
like I have to adjust it too often).
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201105012153
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B9067
e no worse off than we are now, but we don't have to
dive into retraining equal() or touch any other parts of the code.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201104262139
http://biglumber.com/x/web?pk=2529DF6A
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Sounds good to me ... who's volunteering?
(Andrew) I will as well. Github perhaps, Andrew? I'll be happy to get
some unit tests written.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint
clang bug that caused
this was fixed in llvm's HEAD, but HEAD will not compile for me yet, so
I cannot verify it yet. There's a separate bug concerning usage of
plperl, but that's for another day.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.
clang repo and see if it does the
trick.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201011161302
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkzix3IACgkQvJuQZxSWSsgKxQCgl2vbUGS9plb1Zm7Sg+sdKR+5
oIUAn0CI
with clang. Getting that
removed does allow me to do a working make and make check. The make
takes orders of magnitude longer than gcc does, but that's an
issue for another day.
--
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201011160940
http://biglumber.co
ider lowering the bar for a "major"
release, as it's better to err on that side.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201008202330
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkxvSS
ep 50 feet away from all computers.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201008202135
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkxvLZAACgkQvJuQZxSWSsjFcQCeMQX9fQcLZVv6q1wssFIsIMQE
INAAoJPEsMRsezdT2
xample. Consider me a very weak -1
and open to persuasion. :)
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201008202130
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkxvLGQACgkQvJuQZxSWSsjIoQCfY4A
For the record,
I'm with Tom on this: -1 to any changes.
I do like the Ubuntu/Debian way of naming the releases
with some sort of non-numeric name though. :)
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201008202036
http://biglumber.com/
NOT to handle
version numbering. :) I think we got it right the first time.
David Fetter:
> "We're using Postgre 8"
>
> See also all the flocks of tools that claim to support "Postgres 8"
Flocks? Handful at best, and no reason we should be catering to
olution"
as production systems generally avoid full table locks like the plague.
The existing solution works fine as long as we explain that caveat (which
is a little bit of a corner case, else we'd have heard more complaints
before now).
- --
Greg Sabino Mullane g...@turnstep.com
End
s" that started
>> this thread.
> It covers 0% of cases where people are not using psql.
Yes, and everything else already has a "show tables". See
for example, PPA:
http://phppgadmin.sourceforge.net/images/4.png
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corpora
an important goal. Certainly someone
writing a GUI (or a new driver) should be expected to be familiar
with the system catalogs. Moreover, a GUI relies on an underlying
driver, and every driver should already be providing things like
a list of tables natively.
- --
Greg Sabino Mullane g...@tur
2.0
> AJAX thingy - those will likely always use custom catalog queries).
> Maybe a differnet way to look at the whole thing is to reconsider our own
> catalogs (anyone remember newsysview?) and add a bunch of views to abstract
> away most of the current complexity for these usecase
1 - 100 of 423 matches
Mail list logo
