Dear Richard,
I think I use contrib/lo type for manage lo. What is wrong?
Now I have no idea for manage lo on PostgreSQL 8.1.1, I think I need a time to learn.
Could you give me suggestion?
Regards,
Premsun
>>> Richard Huxton 12/13/2005 19:22:01 >>>Premsun Choltanwanich wrote:> Dear
On Tue, Dec 13, 2005 at 11:33:20PM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> writes:
> > The idea is to make a new table in pg_catalog called pg_ddl.
>
> This seems rather poorly thought out --- I can't even tell whether
> your intention is to make a log of past operations,
Yes.
David Fetter <[EMAIL PROTECTED]> writes:
> The idea is to make a new table in pg_catalog called pg_ddl.
This seems rather poorly thought out --- I can't even tell whether your
intention is to make a log of past operations, or to provide a uniform
way to extract the current definition of every obje
Folks,
I've been looking into ways to have a better idea--automatically--of
what's been going on in a database from a DDL level, and here's what
I've come up with so far. I'd much appreciate hearing suggestions
and/or brickbats on this.
The idea is to make a new table in pg_catalog called pg_ddl
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 13, 2005 7:38 PM
> To: Dann Corbit
> Cc: Qingqing Zhou; Luke Lonergan; Neil Conway; Bruce Momjian; pgsql-
> [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Which qsort is used
>
> "Dann Corbit" <[EMAIL PRO
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> The in-order check happens only once
Hm? What about that call inside qloop's loop?
regards, tom lane
---(end of broadcast)---
TIP 6: explain analyze is your friend
Pierre Racine wrote:
> Hi,
>
> This might be a newbie question but I'm wondering how, most of you guys,
> are debugging PostgreSQL on Windows (XP) ? Are you all using gdb? I want to
> develop a new data type and I'd like to trace code in a graphical
> interface. I have been trying very hard wit
Hi,
This might be a newbie question but I'm wondering how, most of you guys, are
debugging PostgreSQL on Windows (XP) ? Are you all using gdb? I want to
develop a new data type and I'd like to trace code in a graphical interface.
I have been trying very hard with Eclipse without success. Insig
Due to a cablemodem failure on Monday, I am offline and will probably
be back online in a few days. You can reach me temporarily at this
email address, [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Have you searched our list archives?
>
> Hi all,
>
> while playing with Npgsql I faced an
> strange behavior of Postgresql server.
>
>
> I have all the details of it and I thought it could be a severe security
> exploit, so I don't send it in clear to this mailing list directly as, I
> think, anybody with this information could Dos po
This user has been unregistered from the lists ... sorry folks ...
On Wed, 14 Dec 2005, [EMAIL PROTECTED] wrote:
kbforge.com is pleased to announce the first public release of "kbforge",
a new free desktop search application specifically designed for software
developers.
What differentiates kb
On Tue, 2005-12-13 at 11:04 -0500, Tom Lane wrote:
> Mario Weilguni <[EMAIL PROTECTED]> writes:
> > I guess two backends might have issued interleaved updates.
> > I think without logging this cannot be solved here.
>
> Yeah, it's annoying that there is no convenient way to see the contents
> of
kbforge.com is pleased to announce the first public release of "kbforge",
a new free desktop search application specifically designed for software
developers.
What differentiates kbforge from other desktop search programs, is its
ability to assist the user in categorising the information before it
On Tue, 2005-12-13 at 22:32 +0100, Joachim Wieland wrote:
> there's a topic that comes up from time to time on the lists, the problem
> that pgsql functions get planned only once and thereafter the same query
> plan is used until server shutdown or explicit recreation of the function.
The problem
Hi,
there's a topic that comes up from time to time on the lists, the problem
that pgsql functions get planned only once and thereafter the same query
plan is used until server shutdown or explicit recreation of the function.
I'd like to implement a way of automatic function replanning. I can thi
I will send you an ANSI C version.
> -Original Message-
> From: Qingqing Zhou [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 13, 2005 1:08 PM
> To: Dann Corbit
> Cc: Tom Lane; Luke Lonergan; Neil Conway; Bruce Momjian; pgsql-
> [EMAIL PROTECTED]
> Subject: RE: [HACKERS] Which qsort is
On Tue, 13 Dec 2005, Dann Corbit wrote:
> The test is designed especially for database systems, which are likely
> to be clustered on data or index (and in the general case are sometimes
> loaded in physically sorted order). In the clustered case, the only
> time the data will not be ordered is
The test is designed especially for database systems, which are likely
to be clustered on data or index (and in the general case are sometimes
loaded in physically sorted order). In the clustered case, the only
time the data will not be ordered is when there has been a page split
and the statistic
The test is O(n)
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 13, 2005 10:51 AM
> To: Dann Corbit
> Cc: Qingqing Zhou; Luke Lonergan; Neil Conway; Bruce Momjian; pgsql-
> [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Which qsort is used
>
> "Dann
Tom Lane schrieb:
"Michael Paesold" <[EMAIL PROTECTED]> writes:
The tests fail for PST/PDT in 2034.
This probably indicates that you've got TZ data reflecting the new US
DST rules. We have not updated the pre-8.0 regression test results
to deal with that.
You're right as far as I can tell
"Dann Corbit" <[EMAIL PROTECTED]> writes:
> Here is a sort template (that can very easily be turned into a C
> routine).
Right offhand I'd guess this to be a loser on not-quite-sorted input,
because the tests it makes to try to prove the input is already sorted
can add significant overhead before
Strike "switches to qsort" insert "switches to heapsort"
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
> [EMAIL PROTECTED] On Behalf Of Dann Corbit
> Sent: Tuesday, December 13, 2005 10:40 AM
> To: Qingqing Zhou; Luke Lonergan
> Cc: Tom Lane; Neil Conway; Bruce Momj
Here is a sort template (that can very easily be turned into a C
routine).
It is an introspective sort. Bentley & McIlroy proved that every qsort
routine will degrade into quadratic behavior with a worst-case input.
This function detects quadratic behavior and switches to qsort when
needed.
Use
On Mon, 12 Dec 2005, Luke Lonergan wrote:
>
> Might you have time to implement these within the testing framework I
> published previously? It has both the NetBSD and qsortG included along with
> a timing routine, etc.
>
Here we go:
http://www.cs.toronto.edu/~zhouqq/postgresql/sort/sort.html
Mario Weilguni <[EMAIL PROTECTED]> writes:
> I guess two backends might have issued interleaved updates.
> I think without logging this cannot be solved here.
Yeah, it's annoying that there is no convenient way to see the contents
of pg_locks at the instant of the deadlock. Knowing which tuple l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn van Oosterhout wrote:
> On Mon, Dec 12, 2005 at 06:26:25PM -0200, Francisco Figueiredo Jr. wrote:
>
> Well, you're not giving any details but if you can cause the server to
> dump core in a standard installation, we're interested. You didn't
>
Am Dienstag, 13. Dezember 2005 16:52 schrieb Tom Lane:
> Mario Weilguni <[EMAIL PROTECTED]> writes:
> > Since the type field is PK, there cannot be 2 rows with type='list', I
> > guess the deadlock must have some different explanation.
>
> Then the deadlock must involve rows in two different tables
Mario Weilguni <[EMAIL PROTECTED]> writes:
> Since the type field is PK, there cannot be 2 rows with type='list', I guess
> the deadlock must have some different explanation.
Then the deadlock must involve rows in two different tables. What else
are you doing in the same transaction(s) as updati
"Michael Paesold" <[EMAIL PROTECTED]> writes:
> The tests fail for PST/PDT in 2034.
This probably indicates that you've got TZ data reflecting the new US
DST rules. We have not updated the pre-8.0 regression test results
to deal with that.
regards, tom lane
-
Am Dienstag, 13. Dezember 2005 16:35 schrieb Tom Lane:
> Mario Weilguni <[EMAIL PROTECTED]> writes:
> > Version: 8.1
> > Query: update last_modified set dataend=now() where type='list'
> > DB-Error : ERROR: deadlock detected
> > DETAIL: Process 10454 waits for ShareLock on transac
Mario Weilguni <[EMAIL PROTECTED]> writes:
> Version: 8.1
> Query: update last_modified set dataend=now() where type='list'
> DB-Error : ERROR: deadlock detected
> DETAIL: Process 10454 waits for ShareLock on transaction 1347632; blocked by
> process 15920.
> Process 15920 waits
Marko Kreen <[EMAIL PROTECTED]> writes:
> http://sourceware.org/ml/libc-alpha/2000-03/msg00139.html
> Seems glibc guys once tested some implementation of quicksort vs. merge sort
> and found out that
>"For small sets and smaller data types (arrays of ints and
>arrays of doubles) mergesort i
"Michael Paesold" <[EMAIL PROTECTED]> writes:
> What about this one from the bug (by Jakub Jelinek):
> ...
> "Performance will be terrible" does not sound that good.
That's the overstatement of the week, though. Jakub is merely unhappy
because some new optimizations won't get applied. At worst -
Attached are regression diffs for 7.4.10, compiled from source on RHEL 3 U6
(gcc 3.2.3 20030502, glibc-2.3.2-95.37) using:
make distclean
./configure '--with-perl' '--prefix=/usr/local/postgresql-7.4.10'
make && make install && make check
The tests fail for PST/PDT in 2034.
Looking at the buil
I got this menssage:
ERROR: could not access status of transaction 3923741036
DETALHE: could not open file "/var/lib/pgsql/data/pg_clog/0E9D": No such file
or directory
when I tried to dump a database on a engine 8.0.3 running on Red Hat 9.0 Linux.
I read about this, but most of then is on en
Premsun Choltanwanich wrote:
Dear All,
I use '$libdir/lo' for manage my Large Object for PostgreSQL 8.0.4 . Now
I try to up my PostgreSQL to new version as 8.1.1 but I think I got some
error about lo (Large Object).
lo (Large Object) function that normally shown in function list now
disapp
Dear All,
I use '$libdir/lo' for manage my Large Object for PostgreSQL 8.0.4 . Now I try to up my PostgreSQL to new version as 8.1.1 but I think I got some error about lo (Large Object).
lo (Large Object) function that normally shown in function list now disappear. I'm sure that I already ch
I've an interesting error with deadlocks on a quite simple table:
Version: 8.1
Query: update last_modified set dataend=now() where type='list'
DB-Error : ERROR: deadlock detected
DETAIL: Process 10454 waits for ShareLock on transaction 1347632; blocked by
process 15920.
Proces
On 12/12/05, Bruce Momjian wrote:
> Qingqing Zhou wrote:
> > Seems we don't link against the port/qsort.c - is there any reason for
> > that? My tests indicates our qsort is much much faster than the libc's.
> Are you willing to say that we should always prefer pgport over glibc's
> qsort()?
I s
Tom Lane wrote:
It seems that gcc is up to some creative reinterpretation of basic C
semantics again; specifically, you can no longer trust that traditional
C semantics of integer overflow hold:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175462
While I don't think we are anywhere usin
40 matches
Mail list logo
