otify abc;
NOTIFY
Asynchronous notification "abc" received from server process with PID 10882.
Asynchronous notification "abc" received from server process with PID 10876.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
signature.asc
Description: Digital signature
input, which warrants more than a notice IMO.
Separately, what are the objections to raising the size limit to 128?
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201211211525
http://bi
ard limit and ERROR instead of truncating and NOTICE?
> Both? Neither because that would break backward compatibility?
My vote is WARNING and bump limit to 128 in 9.3. That's the combo most
likely to make dumb applications work better while not breaking
existing smart ones.
- --
Gr
mentioned in RowExpr or ConvertRowtypeExpr)?
+1
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201207012259
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAk/xDoYACgkQvJuQZxSWSsiFJwCfQBqt/SUkFHeA8FP+mq3nKtW6
r
seen above later on as it sets :scale to 0, multiplies the tpc_b
default number of branches by zero, and then complains when the
minimum number of branches (1) is less than the max allowed (0).
Oddly enough, the code checks for the count(*) < 0 but not <= 0.
--
Greg Sabino Mullane g.
crutable). The bad news is I had to reboot the box for
other reasons and I cannot duplicate the issue. Yet. :)
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpDnyhGQdLj3.pgp
Description: PGP signature
he column types matter: if the only column
is an INT, for example, the problem does not occur.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgp7FCBOAEQDc.pgp
Description: PGP signature
> That's not valid syntax. Some versions of getopt() take it upon
> themselves to rearrange the switch order, some do not ...
Sorry: I should have made clear this happens without the -n as well,
I just wanted to make the sample output a little smaller.
--
Greg Sabino Mullane g...@e
: invalid maximum
number 0
) = 36
write(2, "Client 0 aborted in state 3. Exe"..., 60Client 0 aborted in state 3.
Execution meta-command failed.
) = 60
<>
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpDcL0wQEaVM.pgp
Description: PGP signature
On Mon, May 23, 2011 at 05:04:40PM -0600, Alex Hunsaker wrote:
...
> Greg, can you confirm the attached fixes it for you?
Yes, seems to have done the job, thank you.
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpmugDD5ToZ2.pgp
Description:
alone, but wanted to get the
bug out there so I don't forget about it and in case anyone
wants to take a swing at it. Some Googling suggests it might
be because we are using &PL_sv_undef instead of a proper
newSV(0).
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpNfLiacvvId.pgp
Description: PGP signature
On Mon, May 16, 2011 at 12:57:41PM -0600, Alex Hunsaker wrote:
> > Do we need to apply this patch?
...
> My proposed fix is instead of declaring $_TD in
Yes, please apply, I'm eager to continue testing 9.1 but cannot
proceed until something is in place.
--
Greg Sabino Mullane g..
ne 3.
CONTEXT: compilation of PL/Perl function "wheredidmytdgo"
--
Greg Sabino Mullane g...@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
pgpx7IJuLn2As.pgp
Description: PGP signature
; connection setup and authentication (if found - they'll fallback on
> doing simple auth etc if libpq isn't there)
Yeah, we might end up doing something like that, but it seems
easier from this distance to simply subsume a good copy of
libpq into the DBD::Pg tree. Thanks for the fee
cking everything we can. Why wait until
a future step fails if we can rule it out as early as possible?
We already do that for a number of other things.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 201012291437
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964
have DBD::Pg provide its own libpq. Not
sure if this would enable you to solve the problem or not, but
I suspect it might. Actually removing the libpq dependency is awaiting
copious amounts of free time on my part, or funding from a sponsor.
But it's on the todo list. :)
- --
Greg Sa
quoting for the
very rare case when a value contains one of the special characters.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201006071035
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
--
the first character:
& * ! | > ' " % @ ` #
Same as above, but no quoting if the second character is "safe":
- ? :
Always requires quoting:
":" "#" aka ': ' ' #'
Always requires quoting:
, [ ] { }
Always requir
> So if I understand it correctly, if I need correct transaction behaviour
> in psql even in case of disconnection the only safe way is to use one
> statement per line.
>
> Is this correct?
Yes, that is correct. Pretty big gotcha.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Co
a close eye on the queue today in case it
gets stuck there.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201005121404
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9
gt; always found Bugzilla pretty terrible.
Bugzilla is the worst form of bug tracking out there, except for
all the others.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201004181546
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94
lperl please. :) To that
end, let me know when HEAD has something somewhat stable, and I'll
run some tests against it (e.g. Bucardo, which uses lots of plperl)
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201002251458
http:
ROM def;
EXPLAIN (format YAML) UPDATE abc SET a=a;
EXPLAIN (format JSON) UPDATE abc SET a=a;
EXPLAIN (format XML) UPDATE abc SET a=a;
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200912141230
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B9067149
eb form (and those that do are very
seldom themselves spam. 10% or less sounds about right.
- --
Greg Sabino Mullane g...@turnstep.com
PGP Key: 0x14964AC8 200909291817
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B9067149
row; /* ROW/STATEMENT */
! charactions[5]; /* 1 to 4 of 'i', 'u', 'd', or
't', + trailing \0 */
/* The following are used for referential */
/* integrity constraint triggers *
This was failing:
CREATE TRIGGER foo
AFTER INSERT OR UPDATE OR DELETE OR TRUNCATE
ON foobar
FOR EACH STATEMENT EXECUTE PROCEDURE baz();
Turns out the parser wasn't set up to handle four different trigger
event types. Patch attached.
--
Greg Sabino Mullane g...@endpoint.com g...@turnste
bably a better place to raise a bug.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200903261000
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAknLin4ACgkQvJuQZxSWS
please see
."
It might be nice to upgrade README.HOT to a real documentation page
as well.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200810051758
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iEYEAREDAAYFAkjpOKkACgkQvJuQZxSWSsh
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Does it have pg_index.indcheckxmin = true? If so, see README.HOT.
Yes, that was probably it. Is this worth noting in the documentation somewhere
(other than the technical bowels of HOT)? Perhaps in the CREATE INDEX
docs?
- --
Greg Sab
The following bug has been logged online:
Bug reference: 4410
Logged by: Greg Sabino Mullane
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Linux
Description:Indexes not seen right away
Details:
I cannot reproduce, as this was on a
d to be more efficient. Some related
DBD::Pg attribs to look at are pg_server_prepare and pg_prepare_now.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
End Point Corporation
PGP Key: 0x14964AC8 200803121121
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN P
he switchover at 99 not 100.
Can we switch the default_statistics_target to a default of 100? Is
there any reason not to do so at this point? Ten has always seemed
very low to me, and the 98/99 gotcha only makes the case for at
least 100 as the default stronger.
- --
Greg Sabino Mullane [EMAIL P
ault estimate on our 8.2 boxes. Any particular
number recommended? Any reason why 99 is so magical? I could have sworn I
tried it with 100 last week and saw the bad plan. Guess I should also
boost my default target testing up a bit as well. Thanks for the quick patch,
we'll definitely
I don't have a full test case yet, but I did finally manage to get an
explain analyze to finish in a sane amount of time on 8.2.5. Attached
are two cleaned up explain analyze results, using the exact same data
directory but different executables: one is 8.2.3 and returns as
expected, the other is 8
ry severe to one of our clients. So much so that they may end up going
back to 8.1. The patches to 8.2.5 fix some of the queries, but not all;
some of the problems seem to exist on 8.2.4 as well. We'll try to
develop a self-contained test case that shows the problem, but until then
wanted
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Tom Lane wrote:
> Please try the attached patch (in addition to the one I sent earlier).
This is biting us too, quite badly. Any chance this can get pushed into a
8.2.6?
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964
is is the expected behavior.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200710151809
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFHE+VUvJuQZxSWSsgRAzyGAKCveD8q0a8O2XFEkD1g5f08Z58mbgCgvHUF
z4bBO7MJ0gWow1
LUES (3,1);
DB 2 [0.170] {F6} RUN: COMMIT
DB 1 [1.168] {M5} RUN: INSERT INTO foo VALUES (1)
DB 1 [1.169] {M6} RUN: COMMIT
DB 2 [1.183] {F6} ERROR: DBD::Pg::db commit failed: ERROR: insert or update on
table "bar" violates foreign key constraint "bar_ref_foo"
DETAIL: Key (foo_i
gt; involving MVCC for unlocked lookups and then SnapshotNow for (re)reading
> a table's schema info once we've got lock on it.
No ideas, but a strong +1 for making catalog lookups MVCC. Can this perhaps
become a TODO so we don't forget about it and possibly entice people to
gi
The following bug has been logged online:
Bug reference: 3116
Logged by: Greg Sabino Mullane
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.8
Operating system: Linux
Description:attribute has wrong type
Details:
Reproduced on 8.2.3, 8.1.8, and CVS HEAD
gt; an adequate reason. Is there some major improvement we could make?
Well, as you just pointed out in the last commit, Unicode-aware hashes.
Unicode in general was cleaned up and overhauled in 5.8, so if pl/perl
is going to make a serious attempt to support it, it probably should
require 5.8.
-
minimum requirement for Perl to
5.6 (which came out way back in 2000, so we're unlikely to upset anyone).
If we haven't done that already, this would be a good chance as we
can get rid of that ugly #if block.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200610151328
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> If it gives right answers after you increase work_mem sufficiently,
> I'd bet on this one ...
That's a good bet. Changing it from 1024 to 3500 did the trick ... only
one row returned, even when using the index. Thanks very much!
gt; drop index bigtable_status_partial;
greg=> select (select count(*) from bigtable where status = 'shipped')
+ (select count(*) from bigtable where status <> 'shipped')
UNION select count(*) from bigtable;
?column?
--
1185213
moment -- if someone wants to fix this
> (backport to 8.1 please!), have at it.
Attached is a quick patch for HEAD and 8.1, which should do the job.
Thanks for finding this.
--
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200606301039
http://biglumber.com/x/web?pk=2529DF6AB8F79407
al SQL
used. However, an ORDER BY has no meaning inside of a subselect
passed to IN, as IN treats the list as bag of values, and does not
care about the internal order.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200606011030
http://biglumber.com/x/
The following bug has been logged online:
Bug reference: 1950
Logged by: Greg Sabino Mullane
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 and cvs
Operating system: Linux
Description:Subroutine info cached in pl/perl
Details:
Inner subroutines seem to be
st time for
tablespaces. Also, I would think the no new feature rule could
be bent a little here, considering that psql is a relatively
small standalone app, and, as pointed out, we are definitely going
to see people complain about this on the list. A little bit of
effort now will make the project
for a system call, now it's terminating the postmaster with
> SIBGUS on a call to setproctitle).
I've got valgrind working, but not sure exactly how to use it to debug
this problem. What's the procedure?
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 20
around this locally by not using plperlu
(hence the original reason to switch to another user), but I sure miss
being able to do "use strict" :)
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200508181050
https://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC
The following bug has been logged online:
Bug reference: 1831
Logged by: Greg Sabino Mullane
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux
Description:plperl gives error after reconnect.
Details:
Tested on 8.0.1 and in current
The following bug has been logged online:
Bug reference: 1802
Logged by: Jenny Wang
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.10
Operating system: RedHat 8
Description:index is not a btree
Details:
1 $ cd
$ cd bin
2 $ ./postmaster -D data &
$ .
again since I tweaked the httpd settings,
so I'll assume that was it until I see it again.
Thanks,
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200503290723
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC
r, no more occurances since 16:15 EST.
Thanks,
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200503282200
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFCSMUPvJuQZxSWSsgRAqwnAJ4lGO4ZBboE9xCbva6Wtk2b+MPOaACgxrA9
AoKz1m
a better error message (e.g. pointing
to a corrupt disk or something) would be helpful. The first one was a server
process
and not a background writer process, FWIW.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200503281939
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC
d is probably not an
issue now. Plenty of disk space on the partitions. Suggestions and hints
very welcome.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200503281839
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-BEGIN PGP SIGNATURE-
iD8DBQFCSJazvJuQ
u figure out the problem(s).
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200312182010
-BEGIN PGP SIGNATURE-
iD8DBQE/4lDovJuQZxSWSsgRAulsAJ0bvUiXWiKmUDLV6esHoZtuQ6D5eQCgi5AA
xKH9t+TM59YbXa2dc7CyjRY=
=yapu
-END PGP SIGNATURE-
configure script be made to check
for a proper version of bison?
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200306012154
-BEGIN PGP SIGNATURE-
Comment: http://www.turnstep.com/pgp.html
iD8DBQE+2q7qvJuQZxSWSsgRAjmqAKDOWFXmckpYnvrIXSKVY7CQNWcn2gCbBb7b
il6Rrr+MmQ4fUrFNN4dR
58 matches
Mail list logo
