I said
> One such possible caller is EvalPlanQual. It could go to sleep using
> XactLockTableWait() on the SnapshotDirty's xmax. But the tuple has
> something strange in its xmax -- it's the tuple's cmin actually.
> Leaving this would be probably a bug.
>
> However, if the tuple is new, then Ev
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Release is scheduled for Monday.
I just found a missing "#include " in contrib/tsearch, but
other than that and some release-notes adjustments, this morning's
stable-snapshot build looks shippable. Speak now or hold your peace.
I just built
On Sun, Jun 13, 2004 at 12:24:33AM -0400, [EMAIL PROTECTED] wrote:
> I don't intentially obscure my identification, I just have so much email,
> The last then I want tot do is have my nane skimmed by an outlook email
> virus and blasted everywhere. I also have five enail addresses, person,
> busin
> Thomas Hallgren wrote:
>
>> "Carl E. McMillin" <[EMAIL PROTECTED]> writes:
>>
>>>My name is Carl E. McMillin and I'm still establishing my balance in
>>> this
>>>particular knowledge domain with its nomenclature and entities.
>>>
>>
>> Ok, I was thinking more the name behind [EMAIL PROTECTED] ;-)
d=# update pg_proc set proname = zsubstring(proname,2);
UPDATE 1727
So I say there isn't any reason to prohibit renaming functions just
because they were created at initdb time. The worst-case scenario
is you have to rename 'em back. Likewise for ALTER OWNER.
Again, no reason to stop them doing i
Tablespaces is in the patch queue waiting for Tom's review. Nested
transactions is also in the queue and needs review. Alvaro is working
on implementation of the phantom xid feature, but the patch is probably
ready for application if we think it can all be completed by July 1.
I should have all t
As an example of why superusers should have as few restrictions as
possible, I refer you to the 7.4.2 release notes:
http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-2
Without the ability for superusers to muck with the system catalogs,
we'd have had no choice but to force initdb
Matthew T. O'Connor wrote:
> On Sat, 2004-06-12 at 21:57, Bruce Momjian wrote:
> > We are 12 days into June or roughly 40% into our month extension of the
> > release. I want to report where we are on the big patches.
>
> pg_autovacuum integration is coming along. I submitted a patch a proof
> o
Jan Wieck wrote:
> On 6/12/2004 3:45 PM, Tom Lane wrote:
>
> > Jan Wieck <[EMAIL PROTECTED]> writes:
> >> But a per relation bitmap that tells if a block is a) free of dead
> >> tuples and b) all remaining tuples in it are frozen could be used to let
> >> vacuum skip them (there can't be anythin
On Sat, 2004-06-12 at 21:57, Bruce Momjian wrote:
> We are 12 days into June or roughly 40% into our month extension of the
> release. I want to report where we are on the big patches.
pg_autovacuum integration is coming along. I submitted a patch a proof
of concept patch few days ago. I have d
Jan Wieck <[EMAIL PROTECTED]> writes:
> On 6/12/2004 3:45 PM, Tom Lane wrote:
>> I don't think it would help very much to define a bit like that --- I
>> can't believe that very many pages would contain only frozen tuples,
>> unless you were to adopt an aggressive policy of using VACUUM FREEZE
>> a
We are 12 days into June or roughly 40% into our month extension of the
release. I want to report where we are on the big patches.
Tablespaces is in the patch queue waiting for Tom's review. Nested
transactions is also in the queue and needs review. Alvaro is working
on implementation of the ph
> ...That's one of the reasons I wrote Pl/Java.
More power too you! I'd really like to hear more about this project. Is
http://gborg.postgresql.org/project/pljava/projdisplay.php
your URL?
> In essence, I don't think we disagree on anything.
> The only thing I'm reacting to is the term "app-ser
Thomas Hallgren wrote:
"Carl E. McMillin" <[EMAIL PROTECTED]> writes:
My name is Carl E. McMillin and I'm still establishing my balance in this
particular knowledge domain with its nomenclature and entities.
Ok, I was thinking more the name behind [EMAIL PROTECTED] ;-)
Exactly. I think it's Bill Ga
"Carl E. McMillin" <[EMAIL PROTECTED]> writes:
> My name is Carl E. McMillin and I'm still establishing my balance in this
> particular knowledge domain with its nomenclature and entities.
>
Ok, I was thinking more the name behind [EMAIL PROTECTED] ;-)
> But Postgres isn't purely a storage solutio
On 6/12/2004 3:45 PM, Tom Lane wrote:
Jan Wieck <[EMAIL PROTECTED]> writes:
But a per relation bitmap that tells if a block is a) free of dead
tuples and b) all remaining tuples in it are frozen could be used to let
vacuum skip them (there can't be anything to do). The bit would get
reset whenev
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Anyone else, please test the tar ball for any bug/nits ...
>
> README.CVS is not supposed to appear in the tarball --- whatever Bruce
> thought he did to remove it is not working ...
Removing README.CVS from the tarball is somet
Thanks for your indepth and patient response!
My name is Carl E. McMillin and I'm still establishing my balance in this
particular knowledge domain with its nomenclature and entities.
> The term "App-server" is very commonly used to describe
> the container where the application logic resides. As
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Release is scheduled for Monday.
I'd like to remind people that the pre-release tarball is available from
the ftp servers under /pub/stable_snapshot ... we had complaints last
time that people didn't have a chance to vet the release in advance,
and I don
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Anyone else, please test the tar ball for any bug/nits ...
README.CVS is not supposed to appear in the tarball --- whatever Bruce
thought he did to remove it is not working ...
regards, tom lane
---(
The term "App-server" is very commonly used to describe the container where
the application logic resides. As such, an app-server has access to one or
several Storages. PostgreSQL is an implementation of such a storage. The
thing you describe, "a container for functionality that persists
control/da
Jan Wieck <[EMAIL PROTECTED]> writes:
> But a per relation bitmap that tells if a block is a) free of dead
> tuples and b) all remaining tuples in it are frozen could be used to let
> vacuum skip them (there can't be anything to do). The bit would get
> reset whenever the block is marked dirty.
On 6/10/2004 10:37 AM, Shridhar Daithankar wrote:
[EMAIL PROTECTED] wrote:
The session table is a different issue, but has the same problems. You
have an active website, hundreds or thousands of hits a second, and you
want to manage sessions for this site. Sessions are created, updated many
times,
Tom Lane wrote:
> Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> > I wonder if we could clean up those lost files on database recovery or
> > vacuum.
>
> There is a TODO for this, but it seems exceedingly low priority to me.
>
> In any case I'd not recommend troubling to work on the problem unt
If you consider an app server as a container for functionality that persists
data/control state beyond a single invocation, PostgreSQL (and lots of other
DP solutions, of course) falls into the category already, ne?
I suppose my def. is too gross, but I agree with [EMAIL PROTECTED]'s
conjecture th
I said:
> It's likely that there are some pg_proc entries that you can break the
> system beyond repair by renaming, but I'd expect they are a relatively
> small minority (the system's hardwired references are by OID not name).
Just for fun I tried
d=# update pg_proc set proname = 'z' || proname;
On Sat, 12 Jun 2004, Alvaro Herrera wrote:
> On Sat, Jun 12, 2004 at 10:27:15AM -0700, Stephan Szabo wrote:
>
> > As a question, what was the general assumption about what the following
> > should do (using a modification of the original test case)?
>
> [...]
>
> > Should the statement at (1) fai
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> OK, attached is a file with the original function, and an overloaded one
> that just takes table and column. It searches your current search_path
> to find the first matching table.
The right way to do this at the C level would be to use the
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> I wonder if we could clean up those lost files on database recovery or
> vacuum.
There is a TODO for this, but it seems exceedingly low priority to me.
In any case I'd not recommend troubling to work on the problem until
the tablespaces merry-go-ro
On Thu, 10 Jun 2004, Alvaro Herrera wrote:
> On Wed, Jun 09, 2004 at 11:32:08PM -0700, Stephan Szabo wrote:
>
> > > Unfortunately, I've gotten it to fail, but I haven't looked in depth (I'm
> > > at work, so I'm doing it during compilations and such.)
>
> [...]
>
> > Okay - I think I see what's g
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> I notice you can use most of the RENAME TO commands in postgres to
> rename system objects. Renaming a system table is disallowed:
> test=# alter table pg_namespace rename to blah;
> ERROR: permission denied: "pg_namespace" is a system catal
Even if I find the concepts as such very interesting, I think the term
"Application Server" is very misleading. People would get very confused and
place PostgreSQL in the same category as JBoss, Jonas, Apache Geronimo, IBM
Websphere, BEA Weblogic to name a few well known App-servers.
IMHO, you rea
Jumping on that bandwagon with all 6 feet!
Carl <|};-)>
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, June 11, 2004 9:38 PM
To: [EMAIL PROTECTED]
Subject: [HACKERS] I just got it: PostgreSQL Application Server -- a new
template1=# BEGIN;
BEGIN
template1=# CREATE TABLE foobar (foo char(10));
CREATE TABLE
template1=# select relname, relfilenode from pg_class where
relname='foobar';
relname | relfilenode
-+-
foobar | 66372
(1 row)
> killall -9 postmaster
> ll data/base/1/
-rw--- 1
> Dear [EMAIL PROTECTED] ,
>
>>Maybe we need a pgfoundary project called "PostgreSQL Application
>> Server."
>>Like Apache Tomcat or regular apache or PHP, PostgreSQL could form the
>> SQL
>>base of a far more intricate and flexable framework that encompases a lot
>>of the various features that cou
I notice you can use most of the RENAME TO commands in postgres to
rename system objects. Renaming a system table is disallowed:
test=# alter table pg_namespace rename to blah;
ERROR: permission denied: "pg_namespace" is a system catalog
But mucking with any other system object is not:
test=# a
I'd be inclined to make it only take 2 args, table, col where table can be
namespace qualified. This allows people who arn't namespace aware to just do
SELECT pg_get_serial_sequence('mytable','mycol') and have it return the
correct item following searchpath.. I would think this would then bec
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> >
> > > I surely hope not. Especially not multi-gig databases. The folks running
> > > those should know better than to use Windows, and if they do not, I'll
> > > be happy to tell them so.
You know, it makes
38 matches
Mail list logo
