I was thinking of recommending this to someone, but wanted to try it on my own first; good thing that I did. I think it is broken as of now.I assume that the error thrown for 'select 1', inside a transaction, with 'on_error_rollback on', is not supposed to raise it's head !!!
Or am I missing someth
On Oct 26, 2006, at 18:45, Tom Lane wrote:
log_min_error_statement = error would at least get you the statements
reporting the deadlocks, though not what they're conflicting against.
Would it be possible (in 8.3, say) to log the conflicting backend's
current statement (from pg_stat_activity,
Tom Lane wrote:
> [ Memo to hackers: why is it that log_min_error_statement = error
> isn't the default? ]
I think it default to panic because it's the way to disable the feature,
which was the easiest sell when the feature was introduced. I'm all for
lowering it to error.
--
Alvaro Herrera
Chris Campbell <[EMAIL PROTECTED]> writes:
> Is there additional logging information I can turn on to get more
> details? I guess I need to see exactly what locks both processes
> hold, and what queries they were running when the deadlock occurred?
> Is that easily done, without turning on lo
On Thu, Oct 26, 2006 at 06:11:59PM -0400, Chris Campbell wrote:
> On Oct 26, 2006, at 17:21, Tom Lane wrote:
>
> >And what was 1171 doing? I really doubt that either of these could
> >have
> >been pg_dump.
>
> I know that process 1120 is a Java client (Hibernate) running an
> UPDATE query, b
On Thu, Oct 26, 2006 at 03:06:13PM -0400, Robert Treat wrote:
>
> Unfortunately the techdocs system won't support a url like the one above,
> rather you'll end up with something more like the following
> http://www.postgresql.org/docs/techdocs.54 which is the "GUI Tools Guide"
> (which is link
On Oct 26, 2006, at 17:21, Tom Lane wrote:
And what was 1171 doing? I really doubt that either of these could
have
been pg_dump.
I know that process 1120 is a Java client (Hibernate) running an
UPDATE query, but I have no idea what 1171 is. I doubt that 1171 was
pg_dump, but when we tur
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> 3. Support separate interpreters if possible, refuse to run both plperl
>> and plperlu functions in the same backend if not.
> How would we decide which wins in the third case? "first in" seems
> rather arbitrary. If we went that way
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
You can also examine the output from perl -V
I think we've already established that we won't be able to ignore the
case of not having support for multiple perl interpreters :-(
So it seems we have these choices:
1. Do nothing
Neil Conway <[EMAIL PROTECTED]> writes:
> Note that this patch breaks the translations of these strings, so I
> haven't applied it yet. Should I apply it now, or wait for 8.3 to
> branch?
BTW, unless Peter says it's OK, my advice is to wait. It's already
likely to be the case that translation upd
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> You can also examine the output from perl -V
I think we've already established that we won't be able to ignore the
case of not having support for multiple perl interpreters :-(
So it seems we have these choices:
1. Do nothing (document it as a feature
Chris Campbell <[EMAIL PROTECTED]> writes:
> ERROR: deadlock detected
> DETAIL: Process 1120 waits for ShareLock on transaction 5847116;
> blocked by process 1171.
> Process 1171 waits for ExclusiveLock on tuple (6549,28) of relation
> 37637 of database 37574; blocked by process 1120.
> Relati
On 10/26/06, Gregory Stark <[EMAIL PROTECTED]> wrote:
I think what you want is to add a new method entry in pg_type to
allow a type to declare a method to tell you whether a change
is work-free or not. Then any type, even user-defined types,
can allow some changes to be work-free and some not wit
Andrej Ricnik-Bay wrote:
On 10/27/06, Jim C. Nasby <[EMAIL PROTECTED]> wrote:
Undef in Slackware 10.2
Def in Ubuntu 6.06
Undef in Mandriva 2006
Undef in Solaris 10 06
Def in SLES 9.2
Perl 5.8 in SLES 8.1 throws a fit:
"Array found where operator expected at
/usr/lib/perl5/5.8.0/warnings.pm line 2
We're getting deadlock error messages in the production database logs
during times of inactivity, where the only other thing using the
database (we think) is the every-15-minutes pg_dump process. There
are still database connections up-and-running from unused Hibernate
Java processes, but t
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On 10/26/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> This makes some really quite unacceptable assumptions about
>> the meaning and encoding of typmod ...
>
> True, so VARCHAR seems like the only one? That's the only one I've
> really encountered in
On 10/27/06, Jim C. Nasby <[EMAIL PROTECTED]> wrote:
Undef in Slackware 10.2
Def in Ubuntu 6.06
Undef in Mandriva 2006
Undef in Solaris 10 06
Def in SLES 9.2
Perl 5.8 in SLES 8.1 throws a fit:
"Array found where operator expected at
/usr/lib/perl5/5.8.0/warnings.pm line 294, at end of line
Andrew,
> My Debian Sarge (i386) has:
>
> useithreads='define'
> usethreads='define'
> usemultiplicity='define'
I get the same on Ubuntu and SuSE 9.3, so I think those are pervasive
settings for Linux.
Solaris 10update1:
useithreads='undef'
usethreads='undef'
usemultiplicity='undef'
--
--J
Andrew Dunstan wrote:
> Tom Lane wrote:
>> Andrew Dunstan <[EMAIL PROTECTED]> writes:
>>
>>>Now suppose we have more than one interpreter instance running
>>> at the
>>>same time. This is feasible, but only if you used the
>>> Configure option
>>>"-Dusemultiplicity" or th
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On 10/26/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> This makes some really quite unacceptable assumptions about
>> the meaning and encoding of typmod ...
> True, so VARCHAR seems like the only one? That's the only one I've
> really encountered in th
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Now suppose we have more than one interpreter instance running at the
same time. This is feasible, but only if you used the Configure
option
"-Dusemultiplicity" or the options "-Dusethreads -Duseithreads" when
On 10/26/06, Tom Lane <[EMAIL PROTECTED]> wrote:
This makes some really quite unacceptable assumptions about
the meaning and encoding of typmod ...
True, so VARCHAR seems like the only one? That's the only one I've
really encountered in the field on a fairly regular basis.
I'm also wondering
On Thu, 26 Oct 2006, Alvaro Herrera wrote:
> Jeff Trout wrote:
> >
> > On Oct 26, 2006, at 3:23 PM, Martijn van Oosterhout wrote:
> >
> > >On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
> > >>Perhaps people who use other platforms could look for these flags
> > >>in the
> > >>outp
Jim C. Nasby wrote:
> On Thu, Oct 26, 2006 at 11:59:57AM -0400, Bruce Momjian wrote:
> > Jim C. Nasby wrote:
> > > On Wed, Oct 25, 2006 at 08:42:07PM -0400, Bruce Momjian wrote:
> > > > Jim C. Nasby wrote:
> > > > > Something else worth doing though is to have a paragraph explaining
> > > > > why
On Thu, Oct 26, 2006 at 03:35:11PM -0400, Jeff Trout wrote:
>
> On Oct 26, 2006, at 3:23 PM, Martijn van Oosterhout wrote:
>
> >On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
> >>Perhaps people who use other platforms could look for these flags
> >>in the
> >>output of
> >> p
Jeff Trout wrote:
>
> On Oct 26, 2006, at 3:23 PM, Martijn van Oosterhout wrote:
>
> >On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
> >>Perhaps people who use other platforms could look for these flags
> >>in the
> >>output of
> >> perl -e 'use Config qw(myconfig config_sh c
"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> The attached patch handles the simple case where a user wants to
> increase the user-defined storage size of a variable length object,
> such as VARCHAR or NUMERIC, without having to rebuild the table.
This makes some really quite unacceptable assump
On Oct 26, 2006, at 3:23 PM, Martijn van Oosterhout wrote:
On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
Perhaps people who use other platforms could look for these flags
in the
output of
perl -e 'use Config qw(myconfig config_sh config_vars config_re);
print config_sh()
Andrew Dunstan <[EMAIL PROTECTED]> writes:
>Now suppose we have more than one interpreter instance running at the
>same time. This is feasible, but only if you used the Configure
> option
>"-Dusemultiplicity" or the options "-Dusethreads -Duseithreads" when
>buildi
On Thu, Oct 26, 2006 at 03:15:00PM -0400, Andrew Dunstan wrote:
> Perhaps people who use other platforms could look for these flags in the
> output of
>perl -e 'use Config qw(myconfig config_sh config_vars config_re);
> print config_sh();'
My Debian Sarge (i386) has:
useithreads='define'
us
Andrew Dunstan wrote:
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Anyway, it is probably not expected by many users that loading a
module in plperlu makes it available to plperl - I was slightly
surprised myself to see it work and I am probably more aware than
most of perl a
I wrote:
> Right, but _bt_getstackbuf is working from a search stack created by
> a standard search for the victim page's high key. If that search
> descended through a page to the right of the victim page's actual
> parent, _bt_getstackbuf isn't able to recover.
What I'm tempted to do, at least
On Thursday 26 October 2006 10:45, Andrew Sullivan wrote:
> On Wed, Oct 25, 2006 at 05:46:33PM -0400, Bruce Momjian wrote:
> > Josh Berkus wrote:
> > > So, like www.postgresql.org/docs/techdocs/replication? That would
> > > work.
> >
> > Yes.
>
> I like that idea, but I think that the URL needs t
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Anyway, it is probably not expected by many users that loading a module
in plperlu makes it available to plperl - I was slightly surprised
myself to see it work and I am probably more aware than most of perl and
plperl subtleties.
Neil Conway <[EMAIL PROTECTED]> writes:
> BTW, should pre_auth_delay be included in SHOW ALL?
It's really just a debug aid, so I wouldn't complain if SHOW ALL didn't
show it.
regards, tom lane
---(end of broadcast)---
TIP 2:
On Thu, Oct 26, 2006 at 11:59:57AM -0400, Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > On Wed, Oct 25, 2006 at 08:42:07PM -0400, Bruce Momjian wrote:
> > > Jim C. Nasby wrote:
> > > > Something else worth doing though is to have a paragraph explaining why
> > > > there's no built-in replication.
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Anyway, it is probably not expected by many users that loading a module
> in plperlu makes it available to plperl - I was slightly surprised
> myself to see it work and I am probably more aware than most of perl and
> plperl subtleties.
I think that
HINT: You must specify an operator class for the index or define a
default operator class for the data type.
ERROR: data type character varying has no default operator class for
access method "gist"
use contrib/btree_gist module: compile it and add to your database by command
'psql DB < bt
Recently while doing a little research on how we could do perl module
preloading nicely, I constructed the following:
create function loadmods() returns void language plperlu as $$
use LWP::UserAgent;
$$;
select loadmods();
create function loadurl() returns text language plperl as $$
Any thoughts on the below?
Joshua D. Drake wrote:
> Hello,
>
> I am running into this limitation ALOT with Tsearch2. What are my
> options to get around it. Do I have to compile PostgreSQL with a
> different block size?
>
> If yes, what are the downsides to doing so (outside of not being able to
> The documentation comes with the open source tarball.
Yuck.
>
> I would welcome if the docs point to an unofficial wiki (maintained
> externally from authoritative PostgreSQL developers) or a website
> listing them and giving a brief of each solution.
>
> postgresql.org already does this for e
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> But now that I look at the original post by Ed, I don't see how the
> "failed to re-find parent key" error could result from the issue we've
> been talking about. The error message is printed when _bt_getstackbuf is
> unable to re-find an item i
Tom Lane wrote:
On further reflection, I think I understand why we've not realized the
existence of this bug before: in fact, it *doesn't* lead to wrong search
answers. I think the only visible consequence is exactly the "failed to
re-find parent key" VACUUM error that Ed saw. The reason is tha
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> What does the original research paper by Lanin & Shasha say about this?
Nothing very useful. The connection of our code to that paper is
actually a bit tenuous: their approach to deletion is to make the target
page's key space move left not righ
On Wed, 25 Oct 2006, Josh Berkus wrote:
>
> Bruce,
>
> > It isn't designed for that. It is designed for people to understand
> > what they want, and then they can look around for solutions. I think
> > most agree we don't want a list of solutions in the documentation,
> > though I have a few as
I wrote:
> [ looks at that for a bit... ] Yeah, you're right. Once the deletion
> is completed, the F lower-bound key will disappear from the grandparent,
> which would restore consistency --- but we could have already delivered
> wrong search answers, so that won't do.
On further reflection, I
Thanks for your response.Waiting on anyone to implement this feature ;))-Nick2006/10/23, Jonah H. Harris <[EMAIL PROTECTED]
>:On 10/23/06, Jim C. Nasby <[EMAIL PROTECTED]
> wrote:> Since Jonah hasn't done anything with it he's presumably lost interest,> so you'd need to find someone else lookin
Tom Lane wrote:
In theory, given a slow-enough-moving VACUUM process, this could happen
even without a crash. So I think that means we have to go over to the
other plan of locking everything all the way up to the top of the
deletion before we start doing it --- and also, we'll need crash
recover
Hi,
A typo:
("a write to any server has to be _propogated_")
s/propogated/propagated
Bruce Momjian wrote:
Here is a new replication documentation section I want to add for 8.2:
ftp://momjian.us/pub/postgresql/mypatches/replication
Comments welcomed.
--
Regards,
Alexey Klyukin
I have compiled postgres 1.8.5 on Windows XP from source using MinGW, however the GIST index cannot be created since the following errors pop up:HINT: You must specify an operator class for the index or define a default operator class for the data type.ERROR: data type character varying has no de
Bruce Momjian wrote:
> Jim C. Nasby wrote:
>> On Wed, Oct 25, 2006 at 08:42:07PM -0400, Bruce Momjian wrote:
>>> Jim C. Nasby wrote:
Something else worth doing though is to have a paragraph explaining why
there's no built-in replication. I don't have time to write something
right now
On Mon, Oct 23, 2006 at 05:23:27PM -0400, Tom Lane wrote:
> Mark Kirkwood <[EMAIL PROTECTED]> writes:
> > Right - I think the regression is caused by libc and kernel being built
> > with gcc 3.4.6 and the test program being built with gcc 4.1.2.
>
> Why do you think that? The performance of the
Joshua D. Drake wrote:
> Bruce Momjian wrote:
> > Jim C. Nasby wrote:
> >> On Wed, Oct 25, 2006 at 08:42:07PM -0400, Bruce Momjian wrote:
> >>> Jim C. Nasby wrote:
> Something else worth doing though is to have a paragraph explaining why
> there's no built-in replication. I don't have tim
Jim C. Nasby wrote:
> On Wed, Oct 25, 2006 at 08:42:07PM -0400, Bruce Momjian wrote:
> > Jim C. Nasby wrote:
> > > Something else worth doing though is to have a paragraph explaining why
> > > there's no built-in replication. I don't have time to write something
> > > right now, but I can do it lat
On Wed, Oct 25, 2006 at 08:42:07PM -0400, Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > Something else worth doing though is to have a paragraph explaining why
> > there's no built-in replication. I don't have time to write something
> > right now, but I can do it later tonight if no one beats me
With no new additions submitted today, I have moved my text into our
SGML documentation:
http://momjian.us/main/writings/pgsql/sgml/failover.html
Please let me know what additional changes are needed.
---
bruce wro
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> I don't understand how this "in the meantime" thing works. I tried to
> work out a step-by-step example, could you take a look at it? See
> http://users.tkk.fi/~hlinnaka/pgsql/btree-deletion-bug/
[ looks at that for a bit... ] Yeah, you're right.
Tom Lane wrote:
I wrote:
I've been analyzing Ed L's recent report of index corruption:
http://archives.postgresql.org/pgsql-general/2006-10/msg01183.php
Auch. That's nasty indeed.
So I think the rule needs to be "don't delete the rightmost child unless
it's the only child, in which case you
On Oct 26 05:27, Volkan YAZICI wrote:
> On Oct 26 03:33, FAST PostgreSQL wrote:
> > I couldn't find the CONSTRAINT name ('testconstraint' in this case) being
> > stored in the system catalog. Any idea where I can find it?
>
> AFAIK, it is passed to the related procedure via a DomainIOData struct
On Wed, Oct 25, 2006 at 05:46:33PM -0400, Bruce Momjian wrote:
> Josh Berkus wrote:
> > So, like www.postgresql.org/docs/techdocs/replication? That would work.
>
> Yes.
I like that idea, but I think that the URL needs to be decided upon,
needs to be stable, and needs to be put into the docs. (
On Oct 26 03:33, FAST PostgreSQL wrote:
> I couldn't find the CONSTRAINT name ('testconstraint' in this case) being
> stored in the system catalog. Any idea where I can find it?
AFAIK, it is passed to the related procedure via a DomainIOData struct
that fcinfo->flinfo->fn_extra points to. (See do
Alvaro Herrera napsal(a):
Zdenek Kotala wrote:
Tom Lane napsal(a):
Zdenek Kotala <[EMAIL PROTECTED]> writes:
I prepared patch which use oid output function instead regproc output.
This change works only for COPY TO command.
This is not a bug and we're not going to fix it, most especially not
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> I've looked into this in more depth following your suggestion: I think
> it seems straightforward to move the xl_prev field from being a header
> to a trailer. That way when we do the test on the back pointer we will
> be assured that there is no torn p
Zdenek Kotala wrote:
> Tom Lane napsal(a):
> >Zdenek Kotala <[EMAIL PROTECTED]> writes:
> >>I prepared patch which use oid output function instead regproc output.
> >>This change works only for COPY TO command.
> >
> >This is not a bug and we're not going to fix it, most especially not
> >like tha
Tom Lane napsal(a):
Zdenek Kotala <[EMAIL PROTECTED]> writes:
I prepared patch which use oid output function instead regproc output.
This change works only for COPY TO command.
This is not a bug and we're not going to fix it, most especially not
like that.
OK, The behavior of regproc type i
Hi, we all ready found the problem. I was creating the pg_class structure for 32 fields, but in the creation of Template1 I just inserted 29 initializationvalues, so the problem was that.Just like this:
Wrong CODE:DATA(insert OID = 1259 ( pg_class PGNSP 83 PGUID 0 1259 0 0 0 0 0 f f r 32 0
On Tue, 2006-10-24 at 15:42 -0400, Gregory Stark wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > Simon is essentially arguing that if we are willing to assume no
> > incomplete write() we may as well assume it for WAL too. This seems
> > to me to be raising the risk significantly, but I admit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Oct 23, 2006 at 02:32:47PM -0400, luis garcia wrote:
> Hello, I'm from Venezuela, and I've been making some modifications
> to Postgre's Catalog, but it seems to be a problem creating the Template1
> Database.
>
> When the creation of the data
68 matches
Mail list logo
