*Sigh*, still not having much fun over here:
# gdb /usr/local/pgsql/bin/postgres postgres.36561.core
#0 0x8063b0f in nocachegetattr (tuple=0xbfbfe928, attnum=2,
tupleDesc=0x84ca368, isnull=0xbfbfe7af "") at heaptuple.c:494
494 off = att_addlength(off, att[j]->at
My guess is that FRONTEND is not getting defined anymore, and libpq is
picking up the asserts from dllist.c. Now how did that change. Let me
Cc hackers.
> > ../../../src/interfaces/libpq/libpq.so: undefined reference to `assert_enabled'
>
> Offhand it looks like someone put an Assert() call in
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
>> Hmm. That suggests a clobbered index (as in, first page zeroed out).
> I've rebuilt the whole data structure, as I fear it is a residual of the
> crash we had last week, but, if it means anytyhing, we had done a 'drop
> database/create database'
On Tue, 10 Oct 2000, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > TRAP: Failed Assertion("!(metaopaque->btpo_flags & (1 << 3)):", File: "nbtpage.c
> > ", Line: 181)
>
> Hmm. That suggests a clobbered index (as in, first page zeroed out).
> The Assert report doesn't tell
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> TRAP: Failed Assertion("!(metaopaque->btpo_flags & (1 << 3)):", File: "nbtpage.c
> ", Line: 181)
Hmm. That suggests a clobbered index (as in, first page zeroed out).
The Assert report doesn't tell us which index. Possibly a backtrace
of the coref
altho I'm still investigating, does anyone have an idea why the following
'CREATE TABLE' will cause this erro:
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'playlist_info_pkey
' for table 'playlist_info'
FindExec: found "/pgsql/bin/postgres" using argv[0]
TRAP: Failed Assertion("
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> "bytea for binary data with escapes"??
>>
>> What would those escapes look like? I could not find any escape
>> that would put a NULL character into a bytea field.
> 'a\\0b' put a, NULL, b. You need double-backslash to get one backslash
> to the bac
At 07:55 PM 10/9/00 -0300, The Hermit Hacker wrote:
>> I am not convinced that a 2x penalty for DROP COLUMN is such a huge
>> problem that we should give up all the normal safety features of SQL
>> in order to avoid it. Seems to me that DROP COLUMN is only a big
>> issue during DB development, w
> > Yes, this opens a good question. We have long text fields, and bytea for
> > binary input with escapes. As far as I know, we can store binary values
> > in text fields, but we have no way of getting them in there via SQL
> > queries (except for bytea using escapes for the binary values).
>
Bruce Momjian wrote:
> > On Sat, 07 Oct 2000, Tim Kientzle wrote:
> > > I've been using MySQL for initial development; it has pretty
> > > clean and easy-to-use BLOB support. You just declare a BLOB
> > > column type, then read and write arbitrarily large chunks of data.
> >
> > If you're talking
> > > > > I am not convinced that a 2x penalty for DROP COLUMN is such a huge
> > > > > problem that we should give up all the normal safety features of SQL
> > > > > in order to avoid it. Seems to me that DROP COLUMN is only a big issue
> > > > > during DB development, when you're usually workin
On Mon, 9 Oct 2000, Bruce Momjian wrote:
> > On Mon, 9 Oct 2000, Bruce Momjian wrote:
> >
> > > > The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > > > > hrmm .. mvcc uses a timestamp, no? is there no way of using that
> > > > > timestamp to determine which columns have/haven't been cleaned up
> On Mon, 9 Oct 2000, Bruce Momjian wrote:
>
> > > The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > > > hrmm .. mvcc uses a timestamp, no? is there no way of using that
> > > > timestamp to determine which columns have/haven't been cleaned up
> > > > following a crash? maybe some way of markin
Would it be possible to implement "generic triggers", that is a trigger function for a
whole data base and not only for a single table?
Any elegant way to implement this with existing facilities (other than writing a
trigger function for each of my 250+ tables) ?
Horst
On Mon, 9 Oct 2000, Bruce Momjian wrote:
> > The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > > hrmm .. mvcc uses a timestamp, no? is there no way of using that
> > > timestamp to determine which columns have/haven't been cleaned up
> > > following a crash? maybe some way of marking a table as
On Mon, 9 Oct 2000, Bruce Momjian wrote:
> I need to know how this is different than our current python interface,
> PyGreSQL.
Is this a product of pgsql.com?
Vince.
>
> -- Start of PGP signed section.
> > Announce: First public release of PgSQL Version 1.0
> > ===
On Mon, 2 Oct 2000, Rini Dutta wrote:
> When two tables (table2 and table3) have foreign keys
> referring to a common table(table1), I am unable to
> have 2 concurrent transactions - one performing insert
> on table1 and the other on table2, when the records
> being inserted have the same foreign
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > hrmm .. mvcc uses a timestamp, no? is there no way of using that
> > timestamp to determine which columns have/haven't been cleaned up
> > following a crash? maybe some way of marking a table as being in a 'drop
> > column' mode, so that when i
Try this for both FK tables:
create table tmp2(idx2 int4, col2 int4, constraint
tmpcon2 foreign key(col2) references tmp1(idx) INITIALLY DEFERRED);
This will defer constraint checks till transaction commit...
though constraint triggers should use SnapshotDirty instead of
SELECT FOR UPDATE anyway
> Thus spake Bruce Momjian
> > I have installed this in the current source tree, ready for 7.1.
> >
> > I have installed >
> > > Announce: Release of PyGreSQL version 3.0
>
> When is 7.1 being locked down? I may be releasing 3.1 with a few small
> fixes and changes very soon.
You have until N
I need to know how this is different than our current python interface,
PyGreSQL.
-- Start of PGP signed section.
> Announce: First public release of PgSQL Version 1.0
> ===
>
> PgSQL v1.0 has been released. This is the first public release of PgS
On Thu, 5 Oct 2000, D'Arcy J.M. Cain wrote:
> Thus spake Bruce Momjian
> > I have installed this in the current source tree, ready for 7.1.
> >
> > I have installed >
> > > Announce: Release of PyGreSQL version 3.0
>
> When is 7.1 being locked down? I may be releasing 3.1 with a few small
> f
On Mon, 9 Oct 2000, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > hrmm .. mvcc uses a timestamp, no? is there no way of using that
> > timestamp to determine which columns have/haven't been cleaned up
> > following a crash? maybe some way of marking a table as being in a '
Tom Lane wrote:
>
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > With the number of cron jobs that run a perl script which runs a simple
> > SELECT function(); that does various nightly cleanup or maintenance
> > (billing run) it would be much nicer to have an actual trigger run every
> > 12 hours
Hi there
I have been developing a web application using an
Oracle database on the backend, and Java beans and JSP for the
frontend.
At a late stage in the project I have been asked to
look into the viability of
hosting the application with postgreSQL as the
backend database.
Now my m
Mon, Oct 02, 2000 ve 01:07:46PM -0400 Vince Vielhaber napsal:
# On Mon, 2 Oct 2000, Karel Zak wrote:
#
# >
# > On Mon, 2 Oct 2000, Bruce Momjian wrote:
# >
# > > The only fix is to do
# > >
# > > http://www.cz.postgresql.org/index.html
# >
# > It's returns still same a *bad* result.
#
# Th
Ned Lilly of Great Bridge is finishing up the third day of an on-line
interview accessible through
http://forums.itworld.com/webx?[EMAIL PROTECTED]^3@.ee6d080>.
I'm the moderator of the interview, and have a professional stake in
seeing it attract plenty of readers. More than that, though, I wan
By the way, we finally understood that our main problem,
the one that was making our Pg hang forever, comes from
a deadlock problem. Same as Hannu's one.
There are no deadlock detection, indeed. Good DBAs, or
DBAs working with good coders, will never come across
the problem :) but we did :(
I th
Hey,
I got this error when attempting to setup a table with a trigger that ran a
plpgsql program upon insert:
"DBD::Pg::st execute failed: ERROR: Load of file
/usr/local/pgsql/lib/plpgsql.so failed: ld.so.1:
/usr/local/pgsql/bin/postmaster: fatal: relocation error: file
/usr/local/pgsql/lib/plp
Rod Taylor <[EMAIL PROTECTED]> writes:
> With the number of cron jobs that run a perl script which runs a simple
> SELECT function(); that does various nightly cleanup or maintenance
> (billing run) it would be much nicer to have an actual trigger run every
> 12 hours rather than be initiated by a
Hello,
I have found this problem running Postgre 7.0.2. I am running pg as DB
server
on one internet portal, so I need to solve this problem really fast. I
intend to find
problem in Linux kernel (because of reported problems with VMM allocating
shared
memory), but I would like to ask here, if som
I have compiled and tested PostgreSQL 7.1devel on UnixWare 7.1. During the
process, the need for changes to the FAQ_SCO document was uncovered. The
attach patch file implements thost changes.
*** FAQ_SCO.orig Sat Oct 7 20:50:45 2000
--- FAQ_SCO Sun Oct 8 23:28:08 2000
***
***
At 05:47 PM 10/3/00 -0700, elein wrote:
>
>Hmm, no response on pgsql-general. Anyone up on
>oracle's implementation?
You can subscribe to Oracle's Technet on the web for free (start
at www.oracle.com) and read all their manuals on-line.
AFAIK, Oracle themselves are somewhat up on Oracle's imple
Announce: First public release of PgSQL Version 1.0
===
PgSQL v1.0 has been released. This is the first public release of PgSQL.
It is available at http://sourceforge.net/projects/pgsql.
PgSQL is a package of two (2) modules that provide a Python
> Can I ask about the status of this?
>
> > > > > I modified the current ODBC driver for
> > > > > * referential integrity error reporting,
> > > > > * SELECT in transactions and
> > > > > * disabling autocommit.
> > > > We are starting to think about organizing additional ODBC testing
> > > Yes
Hi,
When two tables (table2 and table3) have foreign keys
referring to a common table(table1), I am unable to
have 2 concurrent transactions - one performing insert
on table1 and the other on table2, when the records
being inserted have the same foreign key.
If I use JDBC, one of the transactio
On Tue, 3 Oct 2000, Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > I always telnet into hub to run autoconf. I have a little script in my
> > ~momjian/bin directory called pgautoconf that does that, and cvs commits
> > the changes.
>
> That's exactly the problem, the version on hub.org
This may seem a little silly, but I'd like to request a feature to
implement timed triggers.
With the number of cron jobs that run a perl script which runs a simple
SELECT function(); that does various nightly cleanup or maintenance
(billing run) it would be much nicer to have an actual trigger r
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> hrmm .. mvcc uses a timestamp, no? is there no way of using that
> timestamp to determine which columns have/haven't been cleaned up
> following a crash? maybe some way of marking a table as being in a 'drop
> column' mode, so that when it gets bro
The Hermit Hacker <[EMAIL PROTECTED]> writes:
>> It is not. The only downside is 2x disk space to make new versions of
>> the tuple.
> huh? vacuum moves/cleans up tuples, as well as compresses them, so that
> the end result is a smaller table then what it started with, at/with very
> little inc
On Mon, 9 Oct 2000, Bruce Momjian wrote:
> > > > Sorry, that's what I meant ... why should marking a column as 'deleted'
> > > > and running a 'vacuum' to clean up the physical table be any less
> > > > crash-safe?
> > >
> > > It is not. The only downside is 2x disk space to make new versions
> > > Sorry, that's what I meant ... why should marking a column as 'deleted'
> > > and running a 'vacuum' to clean up the physical table be any less
> > > crash-safe?
> >
> > It is not. The only downside is 2x disk space to make new versions of
> > the tuple.
>
> huh? vacuum moves/cleans up
On Mon, 9 Oct 2000, Bruce Momjian wrote:
> > On Mon, 9 Oct 2000, Tom Lane wrote:
> >
> > > The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > > >> What happens if you crash partway through?
> > >
> > > > what happens if you crash partway through a vacuum?
> > >
> > > Nothing. Vacuum is crash-s
Can I ask where this was left?
> Hi,
>
> I've managed to speak to someone knowledgeable at Digital in the UK
> who pointed me in the direction of a very interesting include file for
> Digital C/C++, namely /usr/include/alpha/builtins.h.
>
> It contains a series of function prototypes which are
> On Mon, 9 Oct 2000, Tom Lane wrote:
>
> > The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > >> What happens if you crash partway through?
> >
> > > what happens if you crash partway through a vacuum?
> >
> > Nothing. Vacuum is crash-safe. ALTER TABLE should be too.
>
> Sorry, that's what I
On Mon, 9 Oct 2000, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> >> What happens if you crash partway through?
>
> > what happens if you crash partway through a vacuum?
>
> Nothing. Vacuum is crash-safe. ALTER TABLE should be too.
Sorry, that's what I meant ... why shoul
The Hermit Hacker <[EMAIL PROTECTED]> writes:
>> What happens if you crash partway through?
> what happens if you crash partway through a vacuum?
Nothing. Vacuum is crash-safe. ALTER TABLE should be too.
regards, tom lane
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Sorry to be asking again, but any status on this?
At this point I think I can safely say nothing's going to be done for
7.1. It is still an issue that needs to be addressed though.
regards, tom lane
On Mon, 9 Oct 2000, Bruce Momjian wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > >> Basically, move the first 100 rows to the end of the table file, then take
> > >> 100 and write it to position 0, 101 to position 1, etc ... that way, at
> > >> max, you are using ( tuple * 100 ) bytes o
On Mon, 9 Oct 2000, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> Basically, move the first 100 rows to the end of the table file, then take
> >> 100 and write it to position 0, 101 to position 1, etc ... that way, at
> >> max, you are using ( tuple * 100 ) bytes of disk space,
Any comments?
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Is the INSERT rule re-ordering mentioned a TODO item?
>
> Darn if I know. I threw the thought out for discussion, but didn't
> see any comments. I'm not in a hurry to change it, unless there's
> consensus that we should.
>
>
Sorry to be asking again, but any status on this?
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Again, anything to add to the TODO here?
>
> IIRC, there was some unhappiness with the proposal you quote, so I'm
> not sure we've quite agreed what to do... but clearly something must
> be done.
>
Can someone address this?
> Bruce Momjian wrote:
> >
> > Seems this was already done in 7.1, right?
> [thread on puts() and fprintf(stderr and printf instead of tprintf or
> replacement truncated]
>
> There are still scads of fprintf(stderr, "some error message from
> postmaster or backend") ly
> At 09:24 PM 6/8/00 +0900, Tatsuo Ishii wrote:
> >It seems the truncate command deletes all rows from a table even it is
> >referenced by another tables. TRUNCATE is not in the standard any way,
> >so I would not claim this is a bug. However, sometimes it would be
> >helpful for a user to let him
Bruce Momjian wrote:
> Lamar Owen Wrote:
> > And we thought 7.0 had alot of new features relative to 6.5.
> I think the true feature-killer release was 6.5.
Well, this is true. I skipped the whole 6.4 series for a reason :-). I
just _knew_ 6.5 was going to be _it_... (in actuality, it's b
On Sun, 8 Oct 2000, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> The patches ad, ae, and af will cause configure to fail on machines
> >> without mktemp. It's not like things get "screwed up" for me, but the
> >> point of Autoconf is portability to *all* machines, so FreeBSD-
On Sun, 8 Oct 2000, Peter Eisentraut wrote:
> The Hermit Hacker writes:
>
> > Okay, autoconf on hub.org is based on what is in ports ... the only
> > "custom patches" are that which are in /usr/ports/devel/autoconf/patches,
> > and I just went through them and there doesn't look like anything *o
> On Sun, 08 Oct 2000, Bruce Momjian wrote:
> > This will be in 7.1 as WAL (write-ahead log).
>
> What does this exactly mean? Will this WAL be an equivalent of the logical
> log of Informix? Where will they be kept? In the database, as a file, or as
> either?
> Looks pretty good. All that is n
> "Martin A. Marques" wrote:
> >
> > On Sun, 08 Oct 2000, Bruce Momjian wrote:
> > > This will be in 7.1 as WAL (write-ahead log).
> >
> > What does this exactly mean? Will this WAL be an equivalent of the logical
> > log of Informix? Where will they be kept? In the database, as a file, or as
>
Yes, this is true. The API is not isolated for SPI, so you see
everything, including C pollution into the C++ namespace. Not sure
about a solution, except renaming some of the identifiers in the
backend. We have discussed that, and are waiting for more reports of
problems before taking it on.
> On Sat, 07 Oct 2000, Tim Kientzle wrote:
> >
> > I've been using MySQL for initial development; it has pretty
> > clean and easy-to-use BLOB support. You just declare a BLOB
> > column type, then read and write arbitrarily large chunks of data.
> > In Perl, BLOB columns work just like varchar c
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> Basically, move the first 100 rows to the end of the table file, then take
> >> 100 and write it to position 0, 101 to position 1, etc ... that way, at
> >> max, you are using ( tuple * 100 ) bytes of disk space, vs 2x the table
> >> size ... either
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Basically, move the first 100 rows to the end of the table file, then take
>> 100 and write it to position 0, 101 to position 1, etc ... that way, at
>> max, you are using ( tuple * 100 ) bytes of disk space, vs 2x the table
>> size ... either method is
> Basically, move the first 100 rows to the end of the table file, then take
> 100 and write it to position 0, 101 to position 1, etc ... that way, at
> max, you are using ( tuple * 100 ) bytes of disk space, vs 2x the table
> size ... either method is going to lock the file for a period of time,
> Greetings,
>
> Well, it seems that the numeric issue I was having has nothing to do with
> the precision and scale being set the same, it has to do with the input
> data. The precision has to be at least 2 greater than the biggest number
> you need to enter, i.e.
>
> equinox=# create table
Billy G. Allie writes:
> PgSQL v1.0 has been released. This is the first public release of PgSQL.
> It is available at http://sourceforge.net/projects/pgsql.
Sounds interesting, but isn't "pgsql" an extremely unfortunate choice of
name, given that it's already used as an abbreviation for "Postg
Bruce Momjian wrote:
> > > > > PostgreSQL would probably "play" better with other products if
> > > > > the DEBUG macro had a prefix, maybe PGSQLDEBUG or similar.
> > > > >
> > > > > Until there is some fix in this area, plperl will not build with
> > > > > a version of perl that has debugging en
On Sun, 8 Oct 2000, Bruce Momjian wrote:
> Are there any platforms that do not have mktemp? Hard to imagine.
mktemp(1) or mktemp(3)?
The latter is pretty much universal (and dangerous too).
The former is, AFAICS, available only on some Linux and BSD.
But it's under the BSD licence, and is not
"Martin A. Marques" wrote:
>
> On Sun, 08 Oct 2000, Bruce Momjian wrote:
> > This will be in 7.1 as WAL (write-ahead log).
>
> What does this exactly mean? Will this WAL be an equivalent of the logical
> log of Informix? Where will they be kept? In the database, as a file, or as
> either?
> Look
On Sun, 08 Oct 2000, Bruce Momjian wrote:
> This will be in 7.1 as WAL (write-ahead log).
What does this exactly mean? Will this WAL be an equivalent of the logical
log of Informix? Where will they be kept? In the database, as a file, or as
either?
Looks pretty good. All that is needed after th
> > > 2) Implement results as a returned object from pg_database
> > >result = db.exec();
> > >result >> field1 >> field2 >> field3;
> > >and
> > >field = result["field"];
> > >field = result[fieldnum];
Rogue Wave Software has an SQL C++ interface in dbtools.h++. It is
simila
71 matches
Mail list logo
