-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 03 August 2004 12:12 pm, Jonathan Gardner wrote:
I'll look into how to actually implement this at home tonight.
Well, it's two nights later but I think I made some headway. I discovered
the joy that is backend/tcop/postgres.c. I
Hi all,
doing some tests:
regression=# create table test (a integer);
CREATE TABLE
regression=# alter table test add column b test;
ALTER TABLE
regression=# select * from test;
a | b
---+---
(0 rows)
regression=# insert into test values ( 1, (2,null)); --(1)
INSERT 4260928 1
regression=# \d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
is it a paradox or not have table with no column but with rows in in
( I mean, we want it ) ?
Here a way to obtain it.
It's even easier than that actually;
create table test();
insert into test default values;
insert into test
Greg Stark wrote:
Tom Lane [EMAIL PROTECTED] writes:
However, this is probably a bit more work than is reasonable to
undertake right now, when we're already overdue for beta. For the
moment I'm really thinking that we ought to just #ifdef out the %Z
on Windows, and plan to do something nicer
Hey Tom,
Did you rate a mention in the Doom 3 readme file? :)
---
4. COPYRIGHT INFORMATION
DOOM 3 is linked with the JpegLib, copyright (c)1991-1998 Thomas G.
Lane/Independent JPEG Group. All rights reserved.
---
Cool :)
Chris
---(end of
Lol! :)
Hey Tom,
Did you rate a mention in the Doom 3 readme file? :)
---
4. COPYRIGHT INFORMATION
DOOM 3 is linked with the JpegLib, copyright (c)1991-1998 Thomas G.
Lane/Independent JPEG Group. All rights reserved.
---
Cool :)
Chris
---(end of
On Aug 6, 2004, at 12:38 AM, Christopher Kings-Lynne wrote:
4. COPYRIGHT INFORMATION
DOOM 3 is linked with the JpegLib, copyright (c)1991-1998 Thomas G.
Lane/Independent JPEG Group. All rights reserved.
---
Congrats, Mr Lane!
Now, what's Chris doing with Doom 3? :)
Michael Glaesemann
grzm
Christopher Kings-Lynne wrote:
Hey Tom,
Did you rate a mention in the Doom 3 readme file? :)
--- 4. COPYRIGHT INFORMATION
DOOM 3 is linked with the JpegLib, copyright (c)1991-1998 Thomas
G. Lane/Independent JPEG Group. All rights reserved. ---
Cool :)
I remember Lamar Owen had found some site
By accidently passing a NULL pointer in a RuleStmt's RangeVar relname i
recognized
that this can lead to a crash of the backend in the function hashname(),
located in hashfunc.c. It calls strlen() without checking the key pointer
in line 126, which leads on my machine to a null pointer
On Thursday 05 August 2004 06:51 am, Tom Lane wrote:
Jonathan M. Gardner [EMAIL PROTECTED] writes:
except if you look at parse_analyze_varparams it seems that it
*ignores* the numParams and paramTypes passed in. (I could be reading
this wrong, so correct me.)
You're reading it wrong.
Jonathan Gardner [EMAIL PROTECTED] writes:
(1) What's the purpose of specifying the params if it is going to figure it
out on its own?
It may not be able to pick an unambiguous type for an unspecified param.
Consider for instance SELECT abs($1). There isn't any principled way
to pick which of
Bernd Helmle [EMAIL PROTECTED] writes:
By accidently passing a NULL pointer in a RuleStmt's RangeVar relname i
recognized
that this can lead to a crash of the backend in the function hashname(),
located in hashfunc.c.
This is your bug, not hashname's.
regards, tom
In join_selectivity function (plancat.c), a function call is made to
OidFunctionCall4 (fmgr.c), which in turn calls a function pointer.
In need to know what is the actual function being called from
OidFunctionCall4 if the selectivity of mergejoin is the one required from
join_selectivity.
Thanks
Joe Conway wrote:
I'm hesitant to apply the attached this late before the beta without
review, but it seems to take care of the pathological cases I came up
with, doesn't break anything AFAICS, and passes all regression tests. I
guess it can go into beta 2.
I've continued to hack on array
AFAIK there are no major patches still outstanding, with the exception
of the Windows-symlinks patch that arrived today from Andreas. Bruce
and I both think that's worth getting in, if no one has any objections,
but otherwise we essentially have 8.0beta1 code.
The documentation, however,
Joe Conway [EMAIL PROTECTED] writes:
... whitespace just before the delimiter is
significant (even though leading whitespace is not)
Yeah. This has been the documented behavior for quite some time, but
I can't say that I ever liked it.
I view the current behavior as a bug. While making
On Thu, Aug 05, 2004 at 07:58:14PM -0400, Tom Lane wrote:
AFAIK there are no major patches still outstanding, with the
exception of the Windows-symlinks patch that arrived today from
Andreas. Bruce and I both think that's worth getting in, if no one
has any objections, but otherwise we
I've fixed dbsize here and will send it off once I get a second to test it
with multiple tablespaces.
I haven't looked at oid2name.
Bruce put together some ideas a few months back on what we want from
oid2name now (somewhere around here:
If anyone has time to work on docs over the next two days, please show
up on pgsql-docs and let us know what you want to work on. (And of
course it's still open season for bug-fix patches.)
Tom, I haven't had a comment on the 'restoring LOB comments' patch, nor
on the two tablespace failures
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Tom, I haven't had a comment on the 'restoring LOB comments' patch, nor
on the two tablespace failures that Gavin and I brought up (Or the
original schema tablespace problem you found when you committed). They
could probably be post-beta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It`s not a beta-blocker, but I still need to fix the postgresql.conf.sample
file to not use all those commented-out values. Unfortunately, I have not
had time to do this. If someone could take of this, it would be most
appreciated. See Tom`s
For your amusement...
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---BeginMessage---
The start scripts for some daemons do su - user or use
start-stop-daemon -c to launch the daemon, postgresql is one example.
During the time between the daemon launch and it closing it's file
Hi,
I am using postgresql for a system, and having a lot of deadlocks due to
foreign keys. I am aware of the situation regarding this from browsing
the mailing list archives.
As I understand it the solution is to implement dirty reads and modify
the referential integrity triggers to use these
Hi,
i am trying to add some functions to postgresql.
I created a file called ./src/backend/executor/testing.c
then created a file called ./src/include/executor/testing.h
then added testing.o to the OBJS in ./src/backend/executor/Makefile
I included executor/testing.h in execMain.c,
Title: RE: [HACKERS] Anybody have an Oracle PL/SQL reference at hand?
Tom Lane wrote:
Hmm. Not only is that a pretty short list, but many of them don't
correspond very closely to the errors that Postgres would raise.
I think these where like predefined 'shortcuts' for most common
Hi,
I went thru the site
http://www.postgresql.org/docs/7.4/static/wal-benefits-later.html
Undo operation is not implemented. and information of
the status regarding the transaction is stored in the
permanent file pg_clog. But I have not been able to
see the format of the file, as this file is
I've started work on a patch for this problem.
Doing regression tests at present.
I'll get back when done.
Regards,
John
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
On Tue, 2004-08-03 at 23:36, Christopher Kings-Lynne wrote:
I think we need to deny changing column types if a function is using the
table type as a return set.
test=# create table test (a int4);
CREATE TABLE
test=# create function test () returns setof test as 'select 1' language
sql;
FYI, I couldn't find anything in the shell pg_config with this path:
strncat(otherpath, /pgxs/src/makefiles/pgxs.mk, MAXPGPATH-1);
Did you find a mention of this? I looked in pg_config.sh and
Makefile.global.in.
I am not saying your change is wrong, just that it is new, I think.
Peter Eisentraut [EMAIL PROTECTED] writes:
For your amusement...
During the time between the daemon launch and it closing it's file
handles and calling setsid(2) (which some daemons don't do because
they are buggy) any other code running in the same UID could take over
the process via
What is the intended upgrade path for databases using contrib modules?
Because I'm trying to test out my database under a CVS compiled postgres and
running into problems. It seems you can't count on a simple pg_dump/pg_restore
working because functions needed for various operators and index
Yeah, those are all bug fixes and okay for post-beta I think. But which
two tablespace failures are you thinking of exactly? The last couple
weeks have been a bit of a blur for me...
During the time between the daemon launch and it closing it's file
handles and calling setsid(2) (which some daemons don't do because
they are buggy) any other code running in the same UID could take over
the process via ptrace, fork off a child process that inherits the
administrator tty, and
Bruce Momjian [EMAIL PROTECTED] writes:
FYI, I couldn't find anything in the shell pg_config with this path:
strncat(otherpath, /pgxs/src/makefiles/pgxs.mk, MAXPGPATH-1);
Did you find a mention of this? I looked in pg_config.sh and
Makefile.global.in.
The original coding concatenated
Bruce Momjian wrote:
FYI, I couldn't find anything in the shell pg_config with this path:
strncat(otherpath, /pgxs/src/makefiles/pgxs.mk, MAXPGPATH-1);
Did you find a mention of this? I looked in pg_config.sh and
Makefile.global.in.
I see it here:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
I was asked on IRC just why we can't have user=postgres and
group=postgres in the postgresql.conf, and simply when we are run as
root, switch to that user and group.
I should think that running as root up until sometime after we have read
Hi All,
I would like to implement the 'DISABLE TRIGGER' functionality for
Postgres...
My proposal for a syntax are the following. We could choose either or
all of the following
a) ALTER TABLE table_name DISABLE|ENABLE ALL TRIGGERS
(This syntax is available in oracle to alter all
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
FYI, I couldn't find anything in the shell pg_config with this path:
strncat(otherpath, /pgxs/src/makefiles/pgxs.mk, MAXPGPATH-1);
Did you find a mention of this? I looked in pg_config.sh and
Makefile.global.in.
The original coding
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Consider this. Most (well-written) applications are written in three
layers. The data abstraction layer provides a clean interface to the
underlying data so other people don't have to write SQL statements. The
GUI layer handles all the GUI events
Greg Stark [EMAIL PROTECTED] writes:
What is the intended upgrade path for databases using contrib modules?
Normally you just upgrade 'em ...
pg_restore: [archiver (db)] could not execute query: ERROR: could not find function
int2key_in in file /usr/local/pgsql/lib/btree_gist.so
...
Hicham G. Elmongui [EMAIL PROTECTED] writes:
When I tried to gmake, i got the following error message:
Undefined first referenced
symbol in file
PrintPlan
41 matches
Mail list logo