On further thought the real problem is that these numbers are only available
when running with explain on. As shown recently on one of the lists, the
cost of the repeated gettimeofday calls can be substantial. It's not really
feasible to suggest running all queries with that profiling.
On Thu, 27 Nov 2003, Mike Macaskill wrote:
Linux 2.4.20, PG 7.3.2 (this is the box where we wish to run our
application)
HP-UX 11.11, PG 7.3.2, 7.3.4, 7.4 (this is just a test box where PG
installs take less time)
On all of these configurations the the date '1901/12/14' apparently does not
On Wed, 25 Nov 2003, Paul Tuckfield wrote:
I really like the idea of taking a snapshot backup with postgres, using
either volume manager or hardware splits in a disk array to get a
physical backup.
Does anyone else see any value in snapshotting. It would, I image,
essentially work like this:
I ran Tom's second script for two hours on an AMD Duron on Linux 2.4.18.
No problems.
Gavin
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
On Wed, 17 Dec 2003, Bruce Momjian wrote:
Marko Zmak wrote:
I've been usin psql for quite a long time and I found it to be very
comfortable. Since some web providers in my country refuse to put psql
while some thing are still in psql TODO list, I'm interested in
following...
I'd
On Thu, 18 Dec 2003, Tom Lane wrote:
Rod Taylor [EMAIL PROTECTED] writes:
On Thu, 2003-12-18 at 10:20, Tom Lane wrote:
Is there any good reason for this restriction?
The help implies you can.
DECLARE name [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ]
CURSOR [ { WITH | WITHOUT }
On Wed, 21 Jan 2004, Christopher Kings-Lynne wrote:
This is what we did:
0. BEGIN;
1. ALTER TABLE ... SET WITHOUT OIDS
12. ROLLBACK;
13. VACUUM FULL forums_posts;
The problem here is that this conditional doesn't take into account the
change in state which the above transaction causes:
On Wed, 21 Jan 2004, Gavin Sherry wrote:
On Wed, 21 Jan 2004, Christopher Kings-Lynne wrote:
This is what we did:
0. BEGIN;
1. ALTER TABLE ... SET WITHOUT OIDS
12. ROLLBACK;
13. VACUUM FULL forums_posts;
The problem here is that this conditional doesn't take into account
On Fri, 23 Jan 2004, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom's answer will be undoubtly better ...
Nope, I think you got all the relevant points.
The only thing I'd add after having had more time to think about it is
that this seems very much like the problem we
The attached patch changes the existing behaviour of length(char(n)).
Currently, this is what happens:
template1=# select length('blah'::char(10));
length
10
(1 row)
With this patch:
template1=# select length('blah'::char(10));
length
4
(1 row)
This behaviour was
It seems reverse look up for svr1.postgresql.org fails.
Due to this sendmail denies to receive mails relayed by
svr1.postgresql.org (200.46.204.71).
Jan 25 04:09:55 powergres sendmail[9622]:
i0OJ9qY09622:
ruleset=check_rcpt,
arg1=[EMAIL PROTECTED],
On Mon, 8 Feb 2004, Greg Stark wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Edwin S. Ramirez wrote:
Hello,
Is is possible to change the transaction behaviour not to abort when a
syntax error occurs.
I've done some searches on the list, and have not found anything.
No,
On Wed, 11 Feb 2004, Bruce Momjian wrote:
Gavin Sherry wrote:
On Wed, 21 Jan 2004, Gavin Sherry wrote:
On Wed, 21 Jan 2004, Christopher Kings-Lynne wrote:
This is what we did:
0. BEGIN;
1. ALTER TABLE ... SET WITHOUT OIDS
12. ROLLBACK;
13. VACUUM FULL
On Wed, 11 Feb 2004, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
There have been a few discussions about triggers on system tables in
the past and the problems with such triggers seem to be:
I think the killer problem is that we couldn't allow triggers on system
tables to do
On Wed, 11 Feb 2004, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
My idea is to provide a generic interface which is called inside
ProcessUtility() after all other functions are called for the particular
node we're handling. The nodetag itself will be passed to this generic
On Thu, 12 Feb 2004, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
Do you have an example at hand of a system function which will face this
problem so that I can see what is involved?
Mmm ... try CREATE TABLE with foreign keys. IIRC the basic table is
created and then we do
/pgpatches
I will try to apply it within the next 48 hours.
---
Gavin Sherry wrote:
The attached patch changes the existing behaviour of length(char(n)).
Currently, this is what happens:
template1=# select length('blah
Hi all,
I've been looking at implementing table spaces for 7.5. Some notes and
implementation details follow.
--
Type of table space:
There are many different table space implementations in relational
database management systems. In my implementation, a table space in
PostgreSQL will be
Is it possible to put WALs and CLOGs into different tablespaces? (maybe
different RAID systems). Some companies want that ...
I wasn't going to look at that just yet.
There is of course the temporary hack of symlinking WAL else where.
I'd be interested to see the performance difference
On Thu, 26 Feb 2004, Alex J. Avriette wrote:
On Thu, Feb 26, 2004 at 11:22:28PM +1100, Gavin Sherry wrote:
Certainly, table spaces are used in many ways in oracle, db2, etc. You can
mirror data across them, have different buffer sizes for example.
In some implementations, they can be raw
On Thu, 26 Feb 2004, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
A table space is a directory structure. The directory structure is as
follows:
[EMAIL PROTECTED] /path/to/tblspc]$ ls
OID1/ OID2/
OID1 and OID2 are the OIDs of databases which have created a table space
On Thu, 26 Feb 2004, Dennis Bjorklund wrote:
On Thu, 26 Feb 2004, Gavin Sherry wrote:
Comments? Questions? Suggestions?
Is that plan that in the future one can split a single table into
different table spaces? Like storing all rows with year 1999 in one
tablespace and the rest in another
On Fri, 27 Feb 2004 [EMAIL PROTECTED] wrote:
I do not intend to undertake raw disk tablespaces for 7.5. I'd be
interested if anyone could provide some real world benchmarking of file
system vs. raw disk. Postgres benefits a lot from kernel file system
cache
at the moment.
Yes, and
On Tue, 2 Mar 2004, Bruce Momjian wrote:
Gavin Sherry wrote:
The actual creation of the table space will be done with:
CREATE TABLE SPACE name LOCATION /path/to/tblspc;
Seems you should use CREATE TABLESPACE (no space) so it is more distinct
from CREATE TABLE.
Oops. Typo
On Tue, 2 Mar 2004, Bruce Momjian wrote:
Gavin Sherry wrote:
Actually, I think that's a pretty good idea :-). I'd solves a bunch of
issues in the backend (postmaster start up can recurse through
$PGDATA/tablespaces looking for postmaster.pid files) and will also assist
admins
On Wed, 3 Mar 2004, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
For tablespaces on OS's that don't support it, I think we will have to
store the path name in the file and read it via the backend. Somehow we
should cache those lookups.
My feeling is that we need not support
http://developer.postgresql.org/todo.php
Gavin
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
On Sun, 21 Mar 2004, Matthew T. O'Connor wrote:
On Sun, 2004-03-21 at 20:31, Christopher Kings-Lynne wrote:
I think these configuration issues will become a lot easier if you make
the autovacuum daemon a subprocess of the postmaster (like, say, the
checkpoint process). Then you have
On Mon, 22 Mar 2004, Matthew T. O'Connor wrote:
On Sun, 2004-03-21 at 23:00, Bruce Momjian wrote:
C) Most importantly, I'm not backend hacker. If someone wants to do the
initial work of getting it running as a backend process, I can take it
from there. A while ago, Bruce offered to
Ok, thanks for the offer to help, but I think I understated things above
when I said I'll need a little help :-)
I haven't looked at the code but...
I have a few big picture questions. Once pg_autovacuum is launched as a
postmaster sub-process, what changes? That is, currently
On Mon, 22 Mar 2004, Bernd Helmle wrote:
I am currently thinking of updateable views for a possible student research
project. In this
case there comes some points to my mind, i want to share with the list.
a) Definition of an updateable view?
The SQL spec. You should definately get a look
As such, I
think that a vacuum backend for a specific database should be forked upon
the first connect. Also, the backend might like to try and workout if
there are any active backends for its database every so often and if not,
perform a final vacuum (if necessary) and exit, so that we
On Mon, 22 Mar 2004, Tom Lane wrote:
Matthew T. O'Connor [EMAIL PROTECTED] writes:
Well this certainly sounds like something that would be easy to do,
which appeals to me at least as a first cut. Question: Does this mean
that I lose many of the advantages of being in the backend? That
On Tue, 30 Mar 2004, Bruce Momjian wrote:
Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
This might seem a bit silly, but is there any chance we could add a
comment at the end of pg_dump text output that says '-- End of dump'?
Sure --- while you're at it, put a
On Fri, 1 Apr 2004, J. Andrew Rogers wrote:
I may be completely missing the point here, but it looks to me as though
the PITR archival mechanism is also most of a native replication
facility. Is there anyone reason this couldn't be extended to
replication, and if so, is anyone planning on
IIRC BSD stands for Berkeley Standard Distribution, and as PostgreSQL
was originally released as free software from Berkeley under this
license it would be weird indeed to call it anything else.
FWIW, 'Berkeley Software Distribution'.
---(end of
On Sun, 2 May 2004, Bruce Momjian wrote:
Tom Lane wrote:
Philip Warner [EMAIL PROTECTED] writes:
Does this mean that ANALYZE will take an exclusive lock on pg_listener
until the ANALYZE finishes? Or is there some other cause?
ANALYZE does not take an exclusive lock on anything.
On Mon, 3 May 2004, Alvaro Herrera wrote:
On Mon, May 03, 2004 at 02:14:18PM +1000, Gavin Sherry wrote:
It is implemented using shared memory. I got stuck when I considered the
situation where we rung out of shared memory. Some emails in the archive
suggested we just fire all listeners
Hi all,
Attached is a patch against HEAD implementing tablespaces.
I've done some testing on Linux and BSD. I've also compiled without
HAVE_SYMLINK defined -- which determines whether or not tablespaces are
available.
The reason for this is that symlinks are used extensively to simplify
access
On Thu, 20 May 2004, Christopher Kings-Lynne wrote:
You may not distribute this tool without the express written
permission of Mark Russinovich.
Then by no means should *any* of that code be included into PostgreSQL. In
fact, comments should not even make reference to it.
May I point
Only vacuum will reset the insert times to the lowest possible!
What does the vacuum code do?? :-]
Please see the manual and the extensive discussions on this point in the
archives. This behaviour is well known -- though undesirable. It is an
effect of the multi-version concurrency control
On Thu, 26 Sep 2002, Jim Mercer wrote:
the following was sent to the php developer's list, and they came back with:
Isn't it generally better (where better means more secure,
efficient, and easily maintained) to handle database access
control using PostgreSQL's native access
On Thu, 26 Sep 2002, Jim Mercer wrote:
On Fri, Sep 27, 2002 at 11:15:35AM +1000, Gavin Sherry wrote:
On Thu, 26 Sep 2002, Jim Mercer wrote:
I would think so, and IMHO, that's where pgsql access control
belongs, with pgsql.
I totally disagree. It is a language level restriction
Thanks to a user query (handle: lltd, IRC) I came across a bug in the
planner. The query was:
---
select o1.timestamp::date as date, count(*), (select sum(oi.price) from
order o2, order_item oi where oi.order_id = o2.id and
o2.timestamp::date = o1.timestamp::date and o2.timestamp
Hi all,
GCC has supported block re-ordering through __builtin_expect() for some
time. I could not see and cannot recall any discussion of this in the
archives. Has anyone played with GCC block re-ordering and PostgreSQL?
Gavin
---(end of
On 10 Oct 2002, Neil Conway wrote:
Well, I'd assume any C library / compiler of half-decent quality on
any platform would provide assembly optimized versions of common
stdlib functions like memset().
While playing around with memset() on my machine (P4 running Linux,
glibc 2.2.5, GCC
On Mon, 14 Oct 2002, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
On Sat, 12 Oct 2002, Joe Conway wrote:
Tom Lane wrote:
Hackers: we might reasonably fix this by doing a deep copy of the
relcache's trigger info during initResultRelInfo(); or we could fix it
by getting rid
Hi all,
I'm thinking that there is an improvement to vacuum which could be made
for 7.4. VACUUM FULLing large, heavily updated tables is a pain. There's
very little an application can do to minimise dead-tuples, particularly if
the table is randomly updated. Wouldn't it be beneficial if VACUUM
On Wed, 16 Oct 2002, Anuradha Ratnaweera wrote:
Is there any plans to make postgresql multithreading?
Thanks in advance (and also for all who commented to my question
regarding replication.)
Anuradha
NB: please don't open fire to declare war on whether multithreading is
On Wed, 16 Oct 2002, Anuradha Ratnaweera wrote:
On Wed, Oct 16, 2002 at 01:25:23AM -0400, Bruce Momjian wrote:
Anuradha Ratnaweera wrote:
... what I want to know is whether multithreading is likely to get
into in postgresql, say somewhere in 8.x, or even in 9.x?
It may be
On 16 Oct 2002, Hannu Krosing wrote:
On Wed, 2002-10-16 at 05:22, Gavin Sherry wrote:
Hi all,
I'm thinking that there is an improvement to vacuum which could be made
for 7.4. VACUUM FULLing large, heavily updated tables is a pain. There's
very little an application can do to minimise
On Fri, 18 Oct 2002, Tom Lane wrote:
Anyone see a way out of this catch-22? If not, which is the least
bad alternative?
Ultimately, fix TRUNCATE to be transaction safe. This is non-trivial,
I know :-).
Regardless, the first option seems the less of the two evils.
Gavin
On Fri, 18 Oct 2002, Mike Mascari wrote:
Gavin Sherry wrote:
On Fri, 18 Oct 2002, Tom Lane wrote:
Anyone see a way out of this catch-22? If not, which is the least
bad alternative?
Ultimately, fix TRUNCATE to be transaction safe. This is non-trivial,
I know
On 12 Oct 2002, Hannu Krosing wrote:
Alvaro Herrera kirjutas L, 12.10.2002 kell 04:16:
On Fri, Oct 11, 2002 at 07:08:18PM -0700, Jeff Davis wrote:
And it really is a minor matter of convenience. I end up dropping and
recreating all my tables a lot in the early stages of development,
On Sat, 12 Oct 2002, Joe Conway wrote:
Tom Lane wrote:
Hackers: we might reasonably fix this by doing a deep copy of the
relcache's trigger info during initResultRelInfo(); or we could fix it
by getting rid of ri_TrigDesc and re-fetching from the relcache every
time. The former would
On Tue, 26 Nov 2002, Stephan Szabo wrote:
Well, it depends. SQL updatable views are fairly limited from what I
remember and the general write your own update rules is much broader, so I
doubt anyone got terribly excited by doing the limited version. It would
take some work to define what
I want to see:
i) proper resource management a-la Oracle. This would allow a DBA to
limited the amount of time any given user spends in the parser, planner or
executor. It would be limited with a more sophisticated user system,
including things like CREATE USER PROFILE ...
ii) Auditing. Who
On Mon, 2 Dec 2002, Christopher Kings-Lynne wrote:
viii) General advocacy, particularly in pushing mainstream IT media
coverage, conferences and university usage -- both for teaching SQL and
for teach database engineering concepts for senior undergrads.
Definitely. How about a resource
On Mon, 2 Dec 2002, Christopher Kings-Lynne wrote:
I've given a talk in the 2002 honours lecture series at UWA about Postgres
and some of the things it can do. All of those guys were interested.
Especially since the deptartment does a lot of work in genetic algoriithms.
Excellent. Can you
On Tue, 17 Dec 2002, Christopher Kings-Lynne wrote:
Hi guys,
Just a thought - do we explicitly wipe password strings from RAM after using
them?
I just read an article (by MS in fact) that illustrates a cute problem.
Imagine you memset the password to zeros after using it. There is a
On Wed, 18 Dec 2002, Joe Conway wrote:
I've been playing around with making it possible to create user defined guc
variables. This has been discussed, at least in passing, before. And it is
even anticipated in guc.c as a possible future feature:
/*
* Build the sorted array. This is
On Wed, 18 Dec 2002, Bruce Momjian wrote:
What exactly can you do with these variables other than SHOW/SET. Seems
it would be nice if they could be used in queries, like in a special
table like sysvar:
SELECT sysvar.fsync;
Isn't that just identical to having a table?
Gavin
On Sat, 21 Dec 2002, Sander Steffann wrote:
Hi,
On the other hand, in a shared hosting environment, I don't think
anyone would really like to have resource limits. What does it help
if your online shop stops working because too many people are
ordering stuff? IMHO it would be much more
On Sat, 21 Dec 2002, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
... The reason I've been thinking about it is some people I've been
working with at universities have a problem with students effectively
DoSing shared installations to affect assessment. This was something
On 5 Jan 2003, Neil Conway wrote:
On Sun, 2003-01-05 at 17:15, Dave Page wrote:
There were always ads there
Yes -- but AFAIK there were in the process of being phased out
(furthermore, the old site only had ads on the initial mirror page,
whereas they are much more widespread on the new
On Mon, 6 Jan 2003, Tom Lane wrote:
Justin Clift [EMAIL PROTECTED] writes:
We don't support OS/400 yet do we?
Never heard of it. Is it Unix-y? Do you have one available for testing?
I think Justin is refering to the AS/400 operating system. I have never
heard of Postgres supporting this
On Mon, 6 Jan 2003, Dan Langille wrote:
On Mon, 6 Jan 2003, Tom Lane wrote:
Justin Clift [EMAIL PROTECTED] writes:
Info:
http://search400.techtarget.com/sDefinition/0,,sid3_gci331973,00.html
That page quoth
OS/400 and its related software has added support for:
The
On Wed, 8 Jan 2003, Christopher Kings-Lynne wrote:
Hi,
Is there any way of making the 'up' arrow retrieve all of the last multiline
query, instead of just the last line? It's really annoying working with
large multiline queries at the moment...
When you say multiline do you mean this:
On Sat, 11 Jan 2003, Tom Lane wrote:
Mike Mascari [EMAIL PROTECTED] writes:
From: Tom Lane [EMAIL PROTECTED]
That's a rowtype variable, though, not a record variable. I believe our
code will work the same as Oracle for that case.
4 TYPE EmpRec IS RECORD (
5 id NUMBER,
6
On Wed, 15 Jan 2003, mlw wrote:
I just wanted to post this note.
I have been in Oracle hell for four days now, and in between the 5
minutes of work and the hours of watings, dealing with table spaces,
extents, and all that, I just keep thinking about how much easier
PostgreSQL is to
On Mon, 20 Jan 2003, Christopher Kings-Lynne wrote:
I wonder why people ask for better documentation. I think the
documentation is really good. Ever read Oracle stuff? *ugh*.
Ever read MySQL docs - *hack*!!
The documentation definately needs work -- particularly client
library
On Tue, 28 Jan 2003, Bruce Momjian wrote:
Peter Eisentraut wrote:
Bruce Momjian writes:
Due to my error, log_min_error messages went into 7.3.X with the wrong
default, and the wrong listed options.
This fixes the bug in CVS current and 7.3.X. Patch attached.
Why does panic
On Thu, 30 Jan 2003, Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Maybe we should create a new type 'inet6'???
I'd lean towards allowing the existing inet and cidr types to store both
v4 and v6 addresses, if at all possible. Is there a good motivation for
doing
On Sun, 2 Feb 2003, Bruce Momjian wrote:
Kurt Roeckx wrote:
On Sat, Feb 01, 2003 at 02:35:15PM +0900, Curt Sampson wrote:
Sure. But you still want to be able to say (and can say, in some [many?]
socket API implementations) that you want to accept only IPv4 or only IPv6
On 2 Feb 2003, Neil Conway wrote:
On Sun, 2003-02-02 at 15:22, Dave Page wrote:
- Each comment attaches only to the page name, version of the page to
which it was submitted *and* subsequent versions (this is the current
behaviour).
- Each comment should attach to the page name to
On Mon, 3 Feb 2003, Andrew Dunstan wrote:
I'm also fairly sure I saw something like
#define fsync _commit
in the Berkeley DB sources the other day, which might be a clue.
I'll be happy to be corrected, though.
You'd be right:
/*
* Win32 has fsync, getcwd, snprintf and vsnprintf, but
On Mon, 3 Feb 2003, Dann Corbit wrote:
-Original Message-
From: Merlin Moncure [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 3:00 PM
To: Andrew Dunstan
Cc: [EMAIL PROTECTED]
Subject: Re: [HACKERS] Win32 and fsync()
I'm having difficulty digging up the
Hi Chris,
On Wed, 12 Feb 2003, Christopher Kings-Lynne wrote:
Machine:
256MB RAM, FreeBSD 4.7, EIDE HDD, 1 Ghz
Seems like a small amount of memory to be memory based tests with.
What about testing sort_mem as well. It would system to me that there
would be no negative to having infinite
On Sat, 15 Feb 2003, Christopher Kings-Lynne wrote:
I think so - Gavin? As far as I'm aware there's not really anything else
on the open source circuit. There is often a MySQL rep there as well
apparently.
Chris is right. David Axmark (MySQL AB) usually turns up, but he didn't
this year.
On Mon, 17 Feb 2003, Tom Lane wrote:
Neil Conway [EMAIL PROTECTED] writes:
On Mon, 2003-02-17 at 18:39, Tom Lane wrote:
If you release the lock then I think you are opening yourself to worse
troubles than this one, having to do with someone renaming/deleting the
table and/or index out
On 19 Feb 2003, Dave Cramer wrote:
Yes, the company in question is more than evaluating it; this request is
a result of a project to port their application to postgres.
Ahh. I thought you were referring to IBM. That is, that IBM was evaluating
Postgres...
Gavin
On 19 Feb 2003, Dave Cramer wrote:
Justin,
This is certainly the case here. I think IBM is deprecating informix,
and many informix users are being forced to make a change, and they are
seriously considering postgres as an alternative.
Do you have any evidence that they are evaluating it?
On 23 Feb 2003, Rod Taylor wrote:
- Move SEQ_MAXVALUE, SEQ_MINVALUE definitions to sequence.h
- Add check in pg_dump to see if the value returned is the max /min
values and replace with NO MAXVALUE, NO MINVALUE.
- Change START and INCREMENT to use START WITH and INCREMENT BY syntax.
On Tue, 4 Mar 2003, Chris Sutton wrote:
Hello,
I need some insight on the best way to use a RAM drive in a Postgresql
installation. Here is our situation and current setup:
Postgresql 7.2.1
First suggestion: upgrade to 7.2.4 to address several bugs.
The concern of course is if
Seems possible that Lynx timed out and generated and sh left only an
empty file.
Guard against this by writing the output of lynx to a temporary file and
either check it for stuff you expect to be there (!-- comments --?) or
for some reasonable size. There are better was to do this, of course...
On Fri, 21 Mar 2003, Christopher Kings-Lynne wrote:
This behaviour I find unusual:
usa=# explain analyze select user_id, plan_next from users_profiles where
plan_next = '2003-01-01';
QUERY PLAN
On Sat, 22 Mar 2003, Tom Lane wrote:
Joe Conway [EMAIL PROTECTED] writes:
Pretty handy! But I couldn't find it documented anywhere -- is it?
I think Thomas did that in one of his last batches of changes, and then
disappeared without adding the documentation. Feel free to contribute
some.
On Thu, 11 Apr 2002, Christopher Kings-Lynne wrote:
Hi all,
I got these odd messages while doing a vacuum in 7.1.3 0 - any idea what
they mean? I assume it's not fatal as they're just notices, but I've never
had them before and haven't had them since.
NOTICE: RegisterSharedInvalid: SI
On Thu, 11 Apr 2002, Tom Lane wrote:
Gavin Sherry [EMAIL PROTECTED] writes:
PrepareStmt: PREPARE name AS prepare_query types_prepare_clause
prepare_store
There is a reasonably clear problem here. prepare_query encompasses much
of the grammar of the parser so it will definately cause
On Sun, 14 Apr 2002, Bruce Momjian wrote:
Gavin, I will do the legwork on this if you wish. I think we need to
No matter. I intended to submit a patch to fix this.
use DefElem to store the COPY params, rather than using specific fields
in CopyStmt.
DefElem would have required
On Sun, 14 Apr 2002, Bruce Momjian wrote:
Gavin, I see where you are going with the patch; creating a list in
gram.y and stuffing CopyStmt directly there. However, I can't find any
other instance of our stuffing things like that in gram.y. We do have
cases using options like COPY in
On Tue, 16 Apr 2002, Curt Sampson wrote:
[snip]
What I'm thinking would be really cool would be to have an offline
way of creating tables using a stand-alone program that would write
the files at, one hopes, near disk speed.
Personally, I think there is some merit in this. Postgres can be
On Tue, 16 Apr 2002, Curt Sampson wrote:
Given the very low parsing and 'planning' overhead, the real cost would be
WAL (the bootstrapper could fail and render the database unusable) and the
subsequent updating of on-disk relations.
MS SQL Server, when doing a BULK INSERT or BCP, can do
On Tue, 16 Apr 2002, Marc G. Fournier wrote:
Could some ppl test out archives.postgresql.org and let me know if they
notice any differences in speed?
Marc,
A dramatic increase in performance.
Gavin
---(end of broadcast)---
TIP 1: subscribe
On Tue, 16 Apr 2002, Bruce Momjian wrote:
The code that bothered me about the CREATE DATABASE param processing
was:
/* process additional options */
foreach(l, $5)
{
List *optitem = (List *) lfirst(l);
switch (lfirsti(optitem))
{
case 1:
On Tue, 30 Apr 2002, Christopher Kings-Lynne wrote:
We have been very fortunate to have avoided such problems since we
started six years ago, and I hope it never happens.
There sure are a lot of arguments in the hackers list tho :) I do wish
people would be a little less 'ad hominem' in
This small patch reloads dynamic libraries whose modification time is
greater than that at the time it was initially loaded. This means that
connections do not need to be reinitialised when a library is recompiled.
There is a problem with this, however: if dlopen()'ing the new patch
fails, the
On Sun, 5 May 2002 [EMAIL PROTECTED] wrote:
On Sun, 05 May 2002 10:01:57 EDT, the world broke into rejoicing as
mlw [EMAIL PROTECTED] said:
It is sunday morning and I have been musing about some PostgreSQL issues. As
some of you are aware, my dot com, dot died, and I am working on a
Neil,
I've also been thinking about this but haven't had time to collect my
thoughts.
On Wed, 29 May 2002, Neil Conway wrote:
Histogram refinement can take place in two possible ways: online
(as queries are executed, the histograms are updated immediately),
or offline (the necessary data is
On Thu, 13 Jun 2002, Mike Mascari wrote:
CREATE TEMPORARY TABLE
...
ON COMMIT DROP;
pseudo-compatible with the SQL-standard of:
ON COMMIT { DELETE | PRESERVE } ROWS;
so one day PostgreSQL's grammar would look like:
...
ON COMMIT { DROP | { DELETE | PRESERVE } ROWS };
I think
1 - 100 of 479 matches
Mail list logo
