Also, what happens with the size of the WAL logs? Do they just grow forever
eventually filling up your hard drive, or should they reach a stable point where they
tend not to grow any further?
ie. Will we sysadmins have to put cron jobs in to tar/gz old WAL logs or what???
Chris
> -Origin
"Steve Howe" <[EMAIL PROTECTED]> writes:
> create rule blah_update as
> on update to blah
>do
> notify TestEvent;
> UPDATE blah SET n1=n1+1; -- Won't crash the connection
> UPDATE blah SET n1=2 WHERE var_field='aaa' AND n1=1 AND n2=2 AND arr_str IS
> NULL AND m IS NULL; -- Will crash t
Hi Alexander,
I've noticed that the PG 7.03 ipcclean script uses "ps x | grep -s
'postmaster'" to determine if a postmaster daemon is still running,
which at least for Mandrake Linux 7.2 doesn't work as expected. With
this version of linux, the ps & grep combination will find itself and
then ipc
At 22:29 22.01.01, Alfred Perlstein wrote:
>* Peter Mount <[EMAIL PROTECTED]> [010122 13:21] wrote:
> > At 13:18 21/01/01 +0100, Alexander Jerusalem wrote:
> > >Hi all,
> > >
> > >I'm experiencing some strange behaviour with postgresql 7.0.3 on Red Hat
> > >Linux 7. I'm sending lots of insert stat
On Wed, 24 Jan 2001, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > There has been alot of fixing/patches going into the tree ... woudl like
> > to wrap up a beta4 before the weekend, unless there are any objections?
>
> Agreed, we should push out beta4 before most of core le
I have about 20 open 7.1 items that I need to get resolved before I can
start getting the doc TODO list started. The issues relate to JDBC,
ODBC, and lots of other stuff that need to be settled before we can
finalize 7.1.
They can not be easily summarized in one line. You really have to see
the
> The Hermit Hacker <[EMAIL PROTECTED]> writes:
> > There has been alot of fixing/patches going into the tree ... woudl like
> > to wrap up a beta4 before the weekend, unless there are any objections?
>
> Agreed, we should push out beta4 before most of core leaves for
> LinuxWorld.
>
> I'd like
At 21:40 22.01.01, Peter Mount wrote:
>At 13:18 21/01/01 +0100, Alexander Jerusalem wrote:
>>Hi all,
>>
>>I'm experiencing some strange behaviour with postgresql 7.0.3 on Red Hat
>>Linux 7. I'm sending lots of insert statements to the postgresql server
>>>from another machine via JDBC. During tha
FYI, I still have >50 open items. I will post a list.
>
> There has been alot of fixing/patches going into the tree ... woudl like
> to wrap up a beta4 before the weekend, unless there are any objections?
>
>
> Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
>
Thanks. Removed.
> On Tue, 23 Jan 2001, Bruce Momjian wrote:
>
> > I have added this to /contrib for 7.1.
> >
> Not sure if you know this, but you checked in the code compiled and w/
> the .o file...
>
> FYI.
>
> b. palmer, [EMAIL PROTECTED]
> pgp: www.crimelabs.net/bpalmer.pgp5
>
>
--
"Steve Howe" <[EMAIL PROTECTED]> writes:
> Please try this script, it will crash the current connection.
Crash confirmed. Thanks for the report --- I'm on it...
regards, tom lane
I liked the 'idle in trans' because people can search for just the first
word if they want.
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Any solid consensus on this?
>
> I'm for it (given a short status string --- "idle in tx" or "idle in trans"
> seem fine). Marc's for it. Who's against it
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> There has been alot of fixing/patches going into the tree ... woudl like
> to wrap up a beta4 before the weekend, unless there are any objections?
Agreed, we should push out beta4 before most of core leaves for
LinuxWorld.
I'd like to see if I can
On Tue, 23 Jan 2001, Bruce Momjian wrote:
> I have added this to /contrib for 7.1.
>
Not sure if you know this, but you checked in the code compiled and w/
the .o file...
FYI.
b. palmer, [EMAIL PROTECTED]
pgp: www.crimelabs.net/bpalmer.pgp5
> > What I will probably do is make a wrapper around it so it I can do:
> >
> > ls | oidmapper
> >
> > and see the files as table names.
>
> Hmmm I think I can add that to the code..
>
> will try..
>
It has to be pretty smart. Consider this:
$ pwd
/u/pg/data/base/1872
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Any solid consensus on this?
I'm for it (given a short status string --- "idle in tx" or "idle in trans"
seem fine). Marc's for it. Who's against it?
regards, tom lane
If you don't know what is all about read the bottom (I'll requote my posting)
Bruce Momjian wrote:
> > On Fri, 19 Jan 2001, Bruce Momjian wrote:
> > > Seems we decided against this. Sorry.
> >
> > Huh? from reading Tom's response, sounds like it would be something
> > useful? I know I find ha
Alex Pilosov <[EMAIL PROTECTED]> writes:
> Just to clarify for stupid me: you want to remove it and forbid catalog
> updates or remove it and allow catalog updates? (I hope its latter :)
Right, the latter. If anyone is actually using usecatupd to prevent
themselves from shooting themselves in th
By comparing backups, I found
CREATE CONSTRAINT TRIGGER "" AFTER INSERT OR UPDATE ON "person" NOT
DEFERRABLE INITIALLY IMMEDIATE FOR EACH ROW EXECUTE PROCEDURE "RI_FKey_check_ins"
('', 'person', 'subject', 'UNSPECIFIED', 'subjectid', 'id');
Don't know where that came from, but probably operat
Not knowing much about WAL, but understanding a good deal about Oracle's
logs, I read the WAL documentation below. While it is good, after
reading it I am still left with a couple of questions and therefore
believe the doc could be improved a bit.
The two questions I am left with after reading t
There has been alot of fixing/patches going into the tree ... woudl like
to wrap up a beta4 before the weekend, unless there are any objections?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] se
Peter Eisentraut wrote:
>
> The Hermit Hacker writes:
>
> > Is anyone looking at doing this? Is this purely a MySQL-ism, or is it
> > something that everyone else has except us?
> It's not required by SQL, that's for sure. I think in 7.2 we'll tackle
> schema support, which will accomplish
rfb=# insert into person (id,surname) values (2274,'Unknown!');
ERROR: Relation 'subject' does not exist
Correct - where does subject come from?!
rfb=# \d person
Table "person"
Attribute | Type | Modifier
---+---+--
id| bigint|
Hi all!
I'm using the PostgreSQL 7.03 and PHP 4.x to create a DB driven site, which
is intended to work under RedHat.
And I often get very strange errors like
"Warning: PostgreSQL query failed: pqReadData() -- read() failed:
errno=32 Broken pipe in /usr/local/home/httpd/htdocs/zyx/xyz.php on
On Sat, Jan 20, 2001 at 08:06:51PM -0500, Tom Lane wrote:
> What I've done to solve the immediate C++ problem is to take the
> declaration of sys_nerr out of c.h entirely, and put it into the
> two C modules that actually need it. However, I'm still wondering
> whether we should not drop the rang
Helo all,
Please try this script, it will crash the current connection.
I'm using the 01/18/2001 PostgreSQL v7.1 beta3 snapshot.
-- Script begin -
create table blah(
var_field varchar(8),
n1 integer default 23,
n2 integer,
arr_str varchar[],
I haven't tried everything to recover from this yet, but will quickly try to document
the
crash before I lose track of what exactly went into it and what I did: Basically I
deleted
a table and then ran vacuum verbose, with the net result that I cannot connect to this
database anymore with the er
Thanks. Applied.
>
> I would like to do a interface change in pgcrypto. (Good
> timing, I know :)) At the moment the digest() function returns
> hexadecimal coded hash, but I want it to return pure binary. I
> have also included functions encode() and decode() which support
> 'base64' and
Any solid consensus on this?
>
> Well, I'm still for this ... how about something simiple like 'idle in
> trans'? show, and easy to figure out what it means?
>
> On Mon, 22 Jan 2001, Christof Petig wrote:
>
> > If you don't know what is all about read the bottom (I'll requote my posting)
> >
Thanks. Applied.
[ Charset ISO-8859-1 unsupported, converting... ]
> Hello!
>
> Here is a patch to make the current snapshot compile on Win32 (native, libpq
> and psql) again. Changes are:
> 1) psql requires the includes of "io.h" and "fcntl.h" in command.c in order
> to make a call to open()
I have added the URL to the GIST SGML docs.
> Hi,
>
> I've put R-Tree realization using GiST (yet another test of our changes in
> gist code )on my gist page http://www.sai.msu.su/~megera/postgres/gist/
> Also, I've put
I have added this to /contrib for 7.1.
> > I object. The code displays oids and tablenames or relnames. Oid is just
> > the initial, default filename for tables, and may change to something other
> > than the oid. Currently, the reindex code is the only place that could change
> > the relfilenode
Just to clarify for stupid me: you want to remove it and forbid catalog
updates or remove it and allow catalog updates? (I hope its latter :)
On Tue, 23 Jan 2001, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > While I'm at it and before I forget the 76 places one needs to edi
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> We could add transaction data to index tuples but this would increase
> their size by ~ 16bytes.
The increased space is the least of the drawbacks. Consider also the
time needed to maintain N copies of a tuple's commit status instead of
one. Even f
I wrote:
> Given the infrequency of use of postfix operators compared to prefix,
> I am inclined to think that we should change the grammar to make the
> latter easier to use at the expense of the former. On the other hand,
> it seems there's a pretty large risk of backwards-incompatibility here.
> > > But how Oracle handles this?
> >
> > Oracle doesn't have non-overwriting storage manager but uses
> > rollback segments to maintain MVCC. Rollback segments are used
> > to restore valid version of entire index/table page.
>
> Are there any plans to have something like this? I mean
> overwr
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> While I'm at it and before I forget the 76 places one needs to edit to
> add/remove a system catalog column, what are people's feelings about the
> usecatupd column?
Unless someone pops up and says that they're actually using it,
I'd agree with remov
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> This snippet in pg_dumpall
> $PSQL -d template1 -At -F ' ' \
> -c "SELECT datname, usename, pg_encoding_to_char(d.encoding),
> datistemplate, datpath FROM pg_database d LEFT JOIN pg_shadow u ON (datdba
> = usesysid) WHERE datallowconn;" | \
> while
"Roderick A. Anderson" wrote:
> On Tue, 23 Jan 2001, Peter Eisentraut wrote:
> > RPM. That should work, unless the package spec makes some unportable
> > assumptions, such as different file system layouts. But that is often
> > only an annoyance, not a real problem.
> I'm glad to see GreatBridg
[ Charset ISO-8859-1 unsupported, converting... ]
> > I had thought that the pre-commit information could be stored in an
> > auxiliary table by the middleware program ; we would then have
> > to re-implement some sort of higher-level WAL (I thought of the list
> > of the commands performed in t
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I guess we won't need two separate files global.bki and template1.bki
> anymore. That would simplify some things, but maybe it's still a
> stilistic thing.
It's probably not absolutely necessary to have two, but why change it?
This snippet in pg_dumpall
$PSQL -d template1 -At -F ' ' \
-c "SELECT datname, usename, pg_encoding_to_char(d.encoding),
datistemplate, datpath FROM pg_database d LEFT JOIN pg_shadow u ON (datdba
= usesysid) WHERE datallowconn;" | \
while read DATABASE DBOWNER ENCODING ISTEMPLATE DBPATH; do
(l
> I had thought that the pre-commit information could be stored in an
> auxiliary table by the middleware program ; we would then have
> to re-implement some sort of higher-level WAL (I thought of the list
> of the commands performed in the current transaction, with a sequence
> number for each
On Tue, 23 Jan 2001, Peter Eisentraut wrote:
> In general, RPMs only work on systems that are the same as the one they
> were built on, for various degrees of "same". If you're not picking up
> the RPMs from your distributor or you're sure that the builder used the
> same version as you have, it
Tom Lane writes:
> Accordingly, I suggest that initdb -t should be flushed entirely.
I guess we won't need two separate files global.bki and template1.bki
anymore. That would simplify some things, but maybe it's still a
stilistic thing.
--
Peter Eisentraut [EMAIL PROTECTED] http://
Yes, I vote for removal.
> While I'm at it and before I forget the 76 places one needs to edit to
> add/remove a system catalog column, what are people's feelings about the
> usecatupd column?
>
> The use of this field is that, if false, it disallows any direct
> modification of system catalogs
While I'm at it and before I forget the 76 places one needs to edit to
add/remove a system catalog column, what are people's feelings about the
usecatupd column?
The use of this field is that, if false, it disallows any direct
modification of system catalogs, even for superusers. In the past the
Alfred,
Is there a tarbar with the updated files for the vacuum patch? Or,
is there some way to use the 'v.diff' file without the need to modify
the files by hand? I started changing the files by hand, but realized
that there is so much information that I'm bound to make a mistake in
the manu
> This 'pre-commit' 'really commit' two-step (get 'yer cowboy hats, right
> here) is what's needed, and is currently missing from pgsql.
Hello,
I'm very interested in this topic since I am involved in a
distributed, several-PostgreSQLs-backed, open-source,
buzzword-compliant database replic
Poul Laust Christiansen writes:
> I've just moved from Redhat to Mandrake.
>
> But do I have to use the Mandrake RPM? Doesn't the standard RPM work on
> mandrake?
In general, RPMs only work on systems that are the same as the one they
were built on, for various degrees of "same". If you're not
* Bruce Momjian <[EMAIL PROTECTED]> [010123 11:17] wrote:
> [ Charset KOI8-R unsupported, converting... ]
> > > > > The reason you have to visit the main table is that tuple validity
> > > > > status is only stored in the main table, not in each index.
> > > > > See prior discussions in the archiv
* Bruce Momjian <[EMAIL PROTECTED]> [010122 19:55] wrote:
>
> Vadim, did these patches ever make it into 7.1?
According to:
http://www.postgresql.org/cgi/cvsweb.cgi/pgsql/src/backend/parser/gram.y?rev=2.217&content-type=text/x-cvsweb-markup
nope. :(
>
> > We recently had a very satisfactory c
> I'd hate to wait for the Mandrake specific RPM for every release.
I've been building the Mandrake RPMs, and there is currently a small
problem in the build which I haven't had time to pursue (yet). The
Mandrake distro should be available on the postgresql.org ftp site very
soon after release.
[ Charset KOI8-R unsupported, converting... ]
> > > > The reason you have to visit the main table is that tuple validity
> > > > status is only stored in the main table, not in each index.
> > > > See prior discussions in the archives.
> > >
> > > But how Oracle handles this?
> >
> > Oracle doesn'
Bruce,
On Tue, 23 Jan 2001 09:35:49 -0500 (EST)
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> We used someone elses. Here is a copy. Please submit any patches
> against this version.
Sucks found:
- doesn't handle mediumint, converts it to mediuminteger.
The same for bigint, and probably shorting
> > Think I misinterpreted the SQL3 specs WR to this detail. The
> > checks must be made per statement, not at the transaction
> > level. I'll try to fix it, but we need to define what will
> > happen with referential actions in the case of conflicting
> > actions o
I've just moved from Redhat to Mandrake.
But do I have to use the Mandrake RPM? Doesn't the standard RPM work on
mandrake?
What is the difference between these two RPM's?
I'd hate to wait for the Mandrake specific RPM for every release.
Poul L. Christiansen
On Tue, 23 Jan 2001, Lamar Owen wr
> > > The reason you have to visit the main table is that tuple validity
> > > status is only stored in the main table, not in each index.
> > > See prior discussions in the archives.
> >
> > But how Oracle handles this?
>
> Oracle doesn't have non-overwriting storage manager but uses
> rollback s
> > The reason you have to visit the main table is that tuple validity
> > status is only stored in the main table, not in each index.
> > See prior discussions in the archives.
>
> But how Oracle handles this?
Oracle doesn't have non-overwriting storage manager but uses
rollback segments to ma
On Mon, Jan 22, 2001 at 11:55:56PM -0500, Bruce Momjian wrote:
> > On Wed, Dec 27, 2000 at 12:56:26AM -0500, Bruce Momjian wrote:
> > > I have been asked by the major PHP developer Rasmus Lerdorf to see if
> > > the PostgreSQL/PHP interface needs any improvements.
> > >
> > > Is the current Postg
> Denis Perchine <[EMAIL PROTECTED]> writes:
> > I think this question already was raised here, but... Why PostgreSQL
> > does not do this? What are the pros, and contros?
>
> The reason you have to visit the main table is that tuple validity
> status is only stored in the main table, not in each
> Can some PostgreSQL people comment on this? This person wrote a
> MySQL->PostgreSQL converter too. His version is at:
> http://ziet.zhitomir.ua/~fonin/code
-- THIS VERSION IS EXTREMELY BUGSOME ! USE IT ON YOUR OWN RISK !!!
Hmm. My version does not have this feature, but it could be a
Denis Perchine <[EMAIL PROTECTED]> writes:
> I think this question already was raised here, but... Why PostgreSQL
> does not do this? What are the pros, and contros?
The reason you have to visit the main table is that tuple validity
status is only stored in the main table, not in each index. See
Ned Lilly wrote:
>
> Great Bridge makes PostgreSQL 7.0.3 RPMs for 8 different Linux distros
> at http://www.greatbridge.com/download ...
For the record (with permission of Great Bridge a few months back), I
want to thank Great Bridge for helping with the development of the
current Official RPMs,
Here is documentation for WAL, as text for immediate review and as SGML
source, generated from Vadim's original text with my editing.
Please review for correctness.
=== WAL chapter ==
Write-Ahead Logging (WAL) in Postgres
Author: Written by V
Tom Lane wrote:
> "Robert B. Easter" <[EMAIL PROTECTED]> writes:
> > You'll have to check redhat.com or do an rpm query to see if it should be or
> > is installed on RedHat 6.2.
> I believe redhat does ship Postgres RPMs, but they're PG version
> 6.5.something, which is pretty old --- ie, fewer f
Can some PostgreSQL people comment on this? This person wrote a
MySQL->PostgreSQL converter too. His version is at:
http://ziet.zhitomir.ua/~fonin/code
> Bruce,
>
> On Tue, 23 Jan 2001 09:35:49 -0500 (EST)
> Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> > We used someone elses. Her
Great Bridge makes PostgreSQL 7.0.3 RPMs for 8 different Linux distros
at http://www.greatbridge.com/download ...
Tom Lane wrote:
> "Robert B. Easter" <[EMAIL PROTECTED]> writes:
>
>> You'll have to check redhat.com or do an rpm query to see if it should be or
>> is installed on RedHat 6.2.
Hello,
just small question.
I just realized that it seems that Oracle stores indexed values in the index
itself. This mean that it is not necessary to access table when you need to
get only indexed values.
iso table has an index for vin field. Here is an output for different queries.
SQL> exp
"Robert B. Easter" <[EMAIL PROTECTED]> writes:
> You'll have to check redhat.com or do an rpm query to see if it should be or
> is installed on RedHat 6.2.
I believe redhat does ship Postgres RPMs, but they're PG version
6.5.something, which is pretty old --- ie, fewer features and more bugs
tha
On Mon, 22 Jan 2001, Tom Lane wrote:
> Karel Zak <[EMAIL PROTECTED]> writes:
> > I again a little look at aset code and I probably found small performance
> > reserve in small chunks (chunk <= ALLOC_CHUNK_LIMIT) reallocation.
>
> Hmm. I wouldn't have thought that realloc got called often eno
> Comments anyone?
Yes Bruce, I already told about it with Peter in private mails. Because
it's 1/2 of year and nobody answer I already start work on PL/Python.
The PL/Python will in 7.2 - as soon as I can I send some proposal to
hackers list.
Karel
> >
>
On Mon, 22 Jan 2001, Bruce Momjian wrote:
> How are you on Alpha now?
Great! Downloaded 7.1beta3, and it works fine right out of the
box. Built it in the standard way (./configure; make all), and then ran
the regression tests. All 76 of 76 tests passed on my Alpha XLT 366
w/Debian 2.2. I
[ Charset ISO-8859-1 unsupported, converting... ]
>
> > There were only a few to fix, so I fixed them.
> >
> > > Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > > > Which one of these should we use?
> > > > int4 is a data type, int32 isn't. c.h has DatumGetInt8, but no
> > > > DatumGetInt64; i
Justin Clift writes:
> I found the solution to this being to edit the ipcclean script and
> change the "ps x | grep -s 'postmaster'" part to "ps -e | grep -s
> 'postmaster'". This then works correctly with Mandrake 7.2.
A standard way of finding a process by name without the grep itself
appea
> My current version of PostgreSQL (v6.5.3) does not support Chinese
> characters (what I intented to store in the database != what I retrieved
> from it). I wonder where I can get the patch, which allow it to support
> Chinese. Thx in advance.
>
> Peter Cheung
> http://www.borderfree.com
>
Wha
On Friday 19 January 2001 20:28, Cameron Laird wrote:
> > I am a Comp. Sci. student at Ryerson Polytechnic University in toronto. I
> am in the midst of a software engineering project that involves the
> development of a (possibly) relational database on a RedHat 6.2 development
> environment, w
> There were only a few to fix, so I fixed them.
>
> > Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > > Which one of these should we use?
> > > int4 is a data type, int32 isn't. c.h has DatumGetInt8, but no
> > > DatumGetInt64; it also has DatumGetInt32 but no
> DatumGetInt4. fmgr has
Wait
Quoting Fred Yankowski <[EMAIL PROTECTED]>:
> On Mon, Jan 22, 2001 at 10:19:00PM +, Peter Mount wrote:
> > While on this subject, does anyone have a version of cygipc that works
> with
> > the current version of CygWin? What's on postgresql.org doesn't work,
> and
> > the link on the site w
hi, there!
On Mon, 22 Jan 2001, Bruce Momjian wrote:
>
> > This problem with foreign keys has been reported to me, and I have confirmed
> > the bug exists in current sources. The DELETE should succeed:
> >
> > ---
> >
>
80 matches
Mail list logo
