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
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
/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
/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
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
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
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.
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.
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--
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
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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 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
GUC change to "fix", and now (9.0) is the time to
do it.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201002031233
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B9
hing more than a simple boolean GUC
fix, I would be in your corner).
Yes, third-party code will lag behind, but, again, that's the nature of
the game. We didn't wait for every driver, app, and script to support
schemas before we added them in 7.4, for example. We certainly didn't
wai
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> I have written up a set of guidelines for driver development
> based on what I learned working on ruby-pg:
>
> http://wiki.postgresql.org/wiki/Driver_development
...
> I would appreciate comments by anyone (Greg Sabino Mull
a general
solution. Any query with ambiguity in its parameters should explicitly
declare the types, inside the query itself. Having the driver indicate
the type should be the exception, not the rule.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpo
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> * We also discussed the idea of having a NOTIFY command that
> would work from Primary to Standby.
Just curious, what's a use case for this?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.c
id, payload was "$payload"\n};
}
Not sure what you mean by adapting interfaces to send payloads, I imagine
most if not all simply require a NOTIFY to be sent via PQexec.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint
et rid of the pg_enable_utf8 hack) will encompass
payloads as well.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201002181600
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN
>> payloads as well.
> Is that immanent?
Barring sudden free time, funding, and/or a client request, no.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201002181711
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B
atest checkoint" to help it find
that
information, but I'd sure like a more elegant solution. (One could count lines,
but that's presumes the order and number of items will never change).
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corpora
get that information?
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201003091016
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkuWZnAACgkQvJuQZxSWSsiqWgCglhHZ/awR5lSkjPG+yzd05ulz
X6AAn0uvraweuz8pG15OybCyMzgf
doing backslash
commands?
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201004010941
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAku0oqQACgkQvJuQZxSWSsiJmACghUKR/i+uyJ2n+beuAid4w432
s0oAnArOf1npuMF/7QJ87ZVmSY
Patch attached to show the schema *and* table name when doing
a REINDEX DATABASE.
--
Greg Sabino Mullane g...@endpoint.com g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8
Index: backend/commands/indexcmds.c
===
RCS file
lded in, -sql really should as well,
and slightly less so -performance and -interfaces.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201004081214
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B9
Since this is such a thorny problem, and this is a temporary table, why
not just disallow ALTER completely for the first pass?
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201004241201
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGI
column a: "abc"
I had to change the initial table in test/regress/sql/copy2.sql
from a temp table to a real table, as I could not find an easy
way to represent a wild card temp schema name inside of the
test/regres/expected/copy2.out file.
--
Greg Sabino Mullane g...@endpoint.com
nput syntax for integer: "mm"
LINE 1: update public.foo set id='mm';
# delete from public.foo where id = 'mm';
ERROR: invalid input syntax for integer: "mm"
LINE 1: delete from public.foo where id = 'mm';
Yes, I realize those are technically di
h case I think
Certainly that one particular case can be solved by making the
servers be in time sync a prereq for HS working (in the traditional way).
And by "prereq" I mean a "user beware" documentation warning.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation htt
Subject line kind of says it all: LANGUAGE replacement was
introduced in 9.0, but pg_dump is trying it on all versions.
--
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 201005121537
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
diff
ble. If we had a clearer distinction of list topics, I
might support such a move, but we don't, so I can't.
> ... and, for those that have been here awhile, who "should know better",
> why isn't there any self-management of this sort of stuff in the first
> pla
an fold in -sql and -admin. Would anyone argue against rolling those
two (sql and admin) into -general as a first step?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201005141009
http://biglumber.com/x/web?pk=2529DF6AB8F79407E9444
this
>> also depends on how quickly database driver developers can adapt.
DBD::Pg is already patched, and will very likely be released before 9.0
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201005191105
the implementation step to figure out how to represent that in
> the form of tests.
No, that's exactly backwards. We can't define all the things a language
can do, but we can certainly lay out the things that it is not supposed to.
- --
Greg Sabino Mullane g...@turnstep.com
End P
lperl.c
src/pl/plperl/ppport.h
src/pl/plpgsql/src/pl_exec.c
src/pl/plpython/plpython.c
src/pl/tcl/pltcl.c
src/timezone/pgtz.c
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201005211520
http://biglumber.com/x/web?pk=2529DF6AB8F79407
In light of the proposed purging scheme, how would it be able to distinguish
between those two cases (nothing there yet vs. was there but purged)?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201005231646
http:
how will the *function* know, if a superuser and/or some
background process can purge records at any time?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201005240928
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906
was with trying
to build a cross-language generic whitelist. But it looks like the
ship has already sailed upthread and we've more or less got a working
definition. David, I think you started this thread, I assume you have
some concrete reason for asking about this (new trusted language?).
M
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
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
, 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
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-
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
-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
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
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
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|
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
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
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
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
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
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
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
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"
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
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
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...
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
in the same place.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpSmpP1G2bZT.pgp
Description: PGP signature
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
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
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
-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
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
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
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
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
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
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
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
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
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
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
% 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/
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
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
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.
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
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
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
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
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
, which is a bit ugly in its own right but seems like the best
> fix we're likely to get.
>
> Comments, better ideas?
I like #3. If this were a more common event I might lean towards #1
but it's not so #3 seems fine.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corp
meone else to
> work on adding some more error message fields?
I think you might be confusing this with my somewhat more controversial
patch to show schemas when a COPY error occurs. This just changes
the normal output, not the error output. Nobody has complained
about this patch y
1 - 100 of 423 matches
Mail list logo
