Bruce Momjian <[EMAIL PROTECTED]> writes:
> What we really need is for these folks to start finalizing their patches
> and get them submitted.
Eggzackle ... my point is that I see the win32 train leaving the station
pretty soon, and I don't see anyone else ready to get on board.
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Here are features that are being worked on, hopefully for 7.5:
> > o tablespaces (Gavin)
> > o nested transactions (Alvaro)
> > o two-phase commit (Heikki Linnakangas)
> > o integrated pg_autovacuum (O'Connor)
> >
Neil Conway wrote:
> On 28-Apr-04, at 12:12 AM, Bruce Momjian wrote:
> > I never liked "cell" myself. It is too vague to me. But I see your
> > point that list_head you would think returns the head of the list, not
> > the first element in the list.
>
> I'm not sure what you mean: list_head() re
Simon Riggs wrote:
> > When the server is not running there is nothing to archive, so I don't follow
> > this argument.
>
> The running server creates xlogs, which are still available for archive
> even when the server is not running...
>
> Overall, your point is taken, with many additional comm
On 27-Apr-04, at 10:07 PM, Tom Lane wrote:
[ ... on the topic of list_union(), list_union_int() and friends ]
I guess the real question in my mind is whether there is any true gain
in symmetry or readability by doing it this way.
I think there's a small gain: everything else being equal, an API wi
On 28-Apr-04, at 12:12 AM, Bruce Momjian wrote:
I never liked "cell" myself. It is too vague to me. But I see your
point that list_head you would think returns the head of the list, not
the first element in the list.
I'm not sure what you mean: list_head() returns the "head of the list",
which i
Simon Riggs said:
> On Wed, 2004-04-28 at 18:35, Andrew Dunstan wrote:
>> Simon Riggs wrote:
>>
>> >On Wed, 2004-04-28 at 05:00, Bruce Momjian wrote:
>> >
>> >
>> >>What if we added transaction id to log_line_prefix? The user could
>> >>then log all queries and find the xid where they want to stop
dear all
i compiled postgresql7.4 ,but when type in make ,error appeared as following:
bison -y -d gram.y
NONE:0: /usr/bin/m4: ERROR: EOF in string
sed -e 's/yy/plpgsql_yy/g' -e 's/YY/PLPGSQL_YY/g' < y.tab.c > ./pl_gram.c
/bin/sh: line 1: y.tab.c: No such file or directory
make[4]: ***
I'm in the middle of reviewing (read whacking around) Rod Taylor's patch
for multiple operations in ALTER TABLE, so I'm afraid that no patch in
the same area is likely to apply cleanly after the dust settles :-(
OK, Bruce - just ignore the patch I sent in. I'll refactor it after Tom
commits.
Chr
On Wed, 2004-04-28 at 18:35, Andrew Dunstan wrote:
> Simon Riggs wrote:
>
> >On Wed, 2004-04-28 at 05:00, Bruce Momjian wrote:
> >
> >
> >>What if we added transaction id to log_line_prefix? The user could then
> >>log all queries and find the xid where they want to stop, but of course
> >>that
Does anyone know of an open source project that *has* successfully displaced
a market of mature, established products WITHOUT a commercial entity
providing marketing, support & direction?
gcc?
Nope most big houses will use Intel/Borland/Vc++ or whatever comes
with Solaris.
In fact, I can no
On Mon, Apr 26, 2004 at 03:19:21PM -0400, Bruce Momjian wrote:
>
> Has this been resolved?
Not as far as I know. Unfortunately, the problem happened in an
environment I Can't Play With, and I haven't been able to reproduce
it elsewhere. I've been trying some alternative approaches to
causing it
On Tue, 27 Apr 2004, Andrew Payne wrote:
>
> Scott Marlowe wrote:
>
> > While Apache is and has been wildly popular for bulk hosing and domain
> > parking, for serious commercial use, Netscape's enterprise server, now Sun
> > One, has long been a leader in commercial web sites.
>
> Netscrape/Su
Simon Riggs wrote:
On Wed, 2004-04-28 at 05:00, Bruce Momjian wrote:
What if we added transaction id to log_line_prefix? The user could then
log all queries and find the xid where they want to stop, but of course
that assumes they have enabled such logging, and they have access to the
logs.
On Tue, 27 Apr 2004, Richard Huxton wrote:
> On Tuesday 27 April 2004 14:27, Bruce Momjian wrote:
> > Here are features that are being worked on, hopefully for 7.5:
> >
> > o tablespaces (Gavin)
> > o nested transactions (Alvaro)
> > o two-phase commit (Heikki Linnakangas)
> > o
On Wed, 2004-04-28 at 05:00, Bruce Momjian wrote:
> Simon Riggs wrote:
> > On Tue, 2004-04-27 at 21:56, Rod Taylor wrote:
> > > > Overall, I'd refer back to the points Bruce raised - you certainly do
> > > > need a way of finding out the time to recover to, and as others have
> > > > said also, tim
On Wed, 2004-04-28 at 16:14, Peter Eisentraut wrote:
> Am Tuesday 27 April 2004 19:59 schrieb Bruce Momjian:
> > Peter Eisentraut wrote:
> > > Simon Riggs wrote:
> > > > New utility aimed at being located in src/bin/pg_arch
> > >
> > > Why isn't the archiver process integrated into the server?
> >
Andrew Payne wrote:
>
> Bruce wrote:
>
> > > Does anyone know of an open source project that *has* successfully
> displaced
> > > a market of mature, established products WITHOUT a commercial entity
> > > providing marketing, support & direction?
> >
> > Linux. It doesn't have a single company b
Am Monday 26 April 2004 23:11 schrieb Simon Riggs:
> ii) encourage (i.e. force) people using XLogArchive API to run as the
> PostgreSQL owning-user (postgres).
I think this is perfectly reasonable.
---(end of broadcast)---
TIP 9: the planner will i
Am Tuesday 27 April 2004 19:59 schrieb Bruce Momjian:
> Peter Eisentraut wrote:
> > Simon Riggs wrote:
> > > New utility aimed at being located in src/bin/pg_arch
> >
> > Why isn't the archiver process integrated into the server?
>
> I think it is because the archiver process has to be started/stop
Am Tuesday 27 April 2004 22:21 schrieb Simon Riggs:
> > Why isn't the archiver process integrated into the server?
> You ask a reasonable question however. If pg_autovacuum exists, why
> should pg_autoarch not work also?
pg_autovacuum is going away to be integrated as a backend process.
---
Patch posted on the patches list :-)
Let me know what you think.
- thomas
"Joe Conway" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Thomas Hallgren wrote:
> > Some very good suggestions where made here. What happens next? Will this
end
> > up in a TODO list where someone can "cl
Fabien COELHO <[EMAIL PROTECTED]> writes:
> I'm looking into adding sql standard aggregates EVERY/ANY/SOME.
> It seems to me that there is a syntax ambiguity with ANY and SOME:
> CREATE TABLE bla(b BOOL);
> SELECT TRUE = ANY(b) FROM bla;
AFAICS this ambiguity is built into the SQL sta
Jon Jensen wrote:
On Wed, 28 Apr 2004, Christopher Kings-Lynne wrote:
Seriously - I'd like to raise my voice in favor of installing plpgsql
in template1 by default. I haven't heard any good reason not to (nor
even a bad reason).
It has to work with older dumps that will try to recreate
Vinay Jain wrote:
Hi
thank you for such a useful information...
but actually in my case if i keep table in disk it significantly
degrades performance and even for a table of 10 rows it takes 1-2
minutes I think u r not beliving it ! am i right
for example
I create a table in which i use m
> It seems to me that there is a syntax ambiguity with ANY and SOME:
>
> CREATE TABLE bla(b BOOL);
> SELECT TRUE = ANY(b) FROM bla;
>
> Is parsed as an array-operator and there is a semantical error because no
> array is provided. Now ANY could be an aggregate function call, and it
> s
On Wed, Apr 28, 2004 at 12:14:06AM +0100, Simon Riggs wrote:
> Yes. There is Relational OLAP (ROLAP) and Multidimensional OLAP (MOLAP).
> PostgreSQL can be used as a ROLAP server.
For multidimentional on PostgreSQL there is Mondrian:
http://sourceforge.net/projects/mondrian/
--Tim Larson
-
I'm looking into adding sql standard aggregates EVERY/ANY/SOME.
It seems to me that there is a syntax ambiguity with ANY and SOME:
CREATE TABLE bla(b BOOL);
SELECT TRUE = ANY(b) FROM bla;
Is parsed as an array-operator and there is a semantical error because no
array is provided.
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
>> No check is performed for being a superuser, the table owner or that it
>> is a system table when marking an index for clustering:
> I'm about to submit my SET WITHOUT CLUSTER patch, so I'll fix this bug
> in that.
I'm in the middle of revi
On Wed, 28 Apr 2004, Christopher Kings-Lynne wrote:
> >>Seriously - I'd like to raise my voice in favor of installing plpgsql
> >>in template1 by default. I haven't heard any good reason not to (nor
> >>even a bad reason).
>
> It has to work with older dumps that will try to recreate pl/pgsql
>
"=?gb2312?B?y6fDzQ==?=" <[EMAIL PROTECTED]> writes:
> make[4]: Entering directory `/home/sm/pgsql7.4/src/pl/plpgsql/src'
> bison -y -d gram.y
> NONE:0: /usr/bin/m4: ERROR: EOF in string
I'd say you have a broken bison installation; or possibly bison is okay
but m4 isn't (recent bisons depend on m
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Why doesn't this work:
> test=# select oid, relname, indisclustered from pg_index join pg_class
> on indexrelid=oid where indexrelid > 17205;
> ERROR: column "oid" does not exist
The JOIN is a bit like a view --- it doesn't have any system co
dear all
i tried using tcl with ./configure --with-tcl.
errors appear when make:
make[4]: Entering directory `/home/sm/pgsql7.4/src/pl/plpgsql/src'
bison -y -d gram.y
NONE:0: /usr/bin/m4: ERROR: EOF in string
sed -e 's/yy/plpgsql_yy/g' -e 's/YY/PLPGSQL_YY/g' < y.tab.c > ./pl_gram.c
/bin/
> > I thought of BIT_* because it is short and also used by mysql.
> > Ingres has BIT_AND and BIT_OR functions, but they are not aggregates.
> >
> > I don't know where these standards are available online... It seems they
> > are not available:-(
>
> Neil - can you check your SQL2003 copy to see i
On Wed, 28 Apr 2004 00:08:48 -0400, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Is there a special reason for scanning the leaf pages in *logical*
>> order, i.e. by following the opaque->btpo_next links?
>
>Yes. [..] interlocking between indexscans and deletions.
Thanks for refreshing my memory. This
Bruno Wolff III wrote:
The context of my suggestion was for recovering up until a transaction which
messed things up was committed. I did not want the problem transaction to
be committed. If the problem transaction ran for a long time, there might
be other transactions that I want to keep, if possi
scott.marlowe kirjutas T, 27.04.2004 kell 20:43:
> As someone who has discussed this with Tom in the past, I seem to remember
> that there were major issues with handling the system catalogs, because
> internally, the backends treat the identifiers as if they have already
> been quoted.
why no
What scale factor TPC H are you importing?
additionally - might be worth giving the specs of the machine you are
doing this on.
(I seem to recall trying this with Pg 7.2 a while ago without this
issue, mind you - think I had ~1G of Ram and used the scale fact 1
dataset, i.e 1G)
regards
Mark
Is there anything in SQL2003 about such operators? If there is, we
should make sure we use the correct aggregate names.
That's a point!
I thought of BIT_* because it is short and also used by mysql.
Ingres has BIT_AND and BIT_OR functions, but they are not aggregates.
I don't know where these stan
Please could the committers review my code with a view to committing it
onto the main dev branch?
There are additional cosmetic changes likely to be required, such as
removing some dead comments and streamlining log output.
Let me know whether these should occur before or after first commit.
I'l
Dear Tim,
These are execellent proposals. My only remark would be to build a
step-by-step approach.
In a first stage, we could set-up a minimal web page for the Win32 port:
- PostgreSQL Win32 installer (possibly translated),
- translation of the web page in 40 languages,
- step-by-step installat
> > SELECT BIT_OR(aclitem_privs(...)) AS effective_privs
> > FROM ...
> > WHERE aclitem_grantee(...)=... AND ... ;
>
> Is there anything in SQL2003 about such operators? If there is, we
> should make sure we use the correct aggregate names.
That's a point!
I thought of BIT_* because it is short
No check is performed for being a superuser, the table owner or that it
is a system table when marking an index for clustering:
I'm about to submit my SET WITHOUT CLUSTER patch, so I'll fix this bug
in that.
Chris
---(end of broadcast)---
TIP 9: th
Why doesn't this work:
test=# select oid, relname, indisclustered from pg_index join pg_class
on indexrelid=oid where indexrelid > 17205;
ERROR: column "oid" does not exist
I'm _joining_ on the oid column.
If I qualify it, it works:
test=# select pg_class.oid, relname, indisclustered from pg_ind
SELECT BIT_OR(aclitem_privs(...)) AS effective_privs
FROM ...
WHERE aclitem_grantee(...)=... AND ... ;
Is there anything in SQL2003 about such operators? If there is, we
should make sure we use the correct aggregate names.
Chris
---(end of broadcast)--
> > Would it be appropriate to contribute BIT_AND and BIT_OR aggregates
>
> I am confused why you would use bit on integers
Well, (I think) I need them to manipulate pg_catalog's aclitem bitfields.
I plea not guilty for the design of pg_catalog;-)
Moreover, I added aclitem accessors which return
46 matches
Mail list logo
