. Marc? Remember?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
Emeritus or some such. Please make sure that Tom Lockhart and Vadim
get listed that way, at least.
I think the Emeritus word might be too hard for non-native English
speakers, and even for less educated English speakers.
--
Bruce Momjian| http://candle.pha.pa.us
Josh Berkus wrote:
Guys,
Oh, and how about we kill the Image Map of major developers? It's about 4
years out of date, and makes developers.postgresql.org load like molasses in
January.
Agreed. I think Jan is the only one who knows how to updated it. Jan?
--
Bruce Momjian
many tuples the background write added
to the freespace map, so it doesn't vacuum a table that doesn't need it.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
, or something like that, and the checkpoint process can read
from there.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Have you considered having the background writer check the pages it is
about to write to see if they can be added to the FSM, thereby reducing
the need for vacuum?
The 7.4 rewrite of FSM depends on the assumption that all the free
Christopher Kings-Lynne wrote:
Hey - now that we have a branch, is Bruce going to start committed the
pgpatches2 list?
Yes, once my email backlog is cleared --- probably early next week.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED
Greg Stark wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Have you considered having the background writer check the pages it is
about to write to see if they can be added to the FSM, thereby reducing
the need for vacuum? Seems we would need to add a statistics parameter
so
available that people can test,
and he can improve it during the 7.5 development cycle with feedback
from users.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ
development team. We can help these companies also by providing
speaking and trade show opportunities.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can
not
? : is confusing
use them a lot
a.out is your program
there's no U in foobar
and, char (*(*x())[])() is
a function returning a pointer
to an array of pointers to
functions returning char
-- Jon S. Stumpf
--
Bruce Momjian
=# create table foo (f1 int check (f1 0) check (f1 10));
ERROR: check constraint foo_f1 already exists
Is this a TODO to fix?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13
]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
use it. (I guess the idea
is that all those Windows users can't be wrong. Oh, wait. . .)
You have heard the term first adopters. These people want to be
second adopters. :-)
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359
dunno, I keep trying to keep the
points off my hair.
Maybe a developer of the month feature. :-)
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can
Christopher Browne wrote:
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Bruce Momjian) wrote:
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
As a matter of fact, people who have performance problems are likely to
be the same who have upgrade problems
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
regression=# create table foo (f1 int check (f1 0) check (f1 10));
ERROR: check constraint foo_f1 already exists
Is this a TODO to fix?
Probably should be. I'd be inclined to try to fix it by generating
Jan Wieck wrote:
Bruce Momjian wrote:
Jan Wieck wrote:
If the system is write-bound, the checkpointer will find that many dirty
blocks that he has no time to nap and will burst them out as fast as
possible anyway. Well, at least that's the theory.
PostgreSQL with the non
Jan Wieck wrote:
Bruce Momjian wrote:
Jan Wieck wrote:
What doing frequent fdatasync/fsync during a constant ongoing checkpoint
will cause is to significantly lower the physical write storm happening
at the sync(), which is causing huge problems right now.
I don't see
What is the current schedule for RC2/final?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania
This this a new TODO?
---
Jan Wieck wrote:
Gaetano Mendola wrote:
Bruce Momjian wrote:
I can confirm this bug in CVS.
Dropping the pkey from table b in fact drops the unique index from it.
The SPI plan cached
Source code cleanup
o Features/fixes
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
Marc G. Fournier wrote:
On Fri, 7 Nov 2003, Bruce Momjian wrote:
Here are the major things I do for the PostgreSQL project. Are there
some items I should be doing more/less of?
o Patches
o TODO/FAQ
o Email discussion, coordination
o Win32
o Talks
Peter Eisentraut wrote:
Bruce Momjian writes:
o TODO/FAQ
The FAQ might as well be maintained just like the rest of the
documentation, i.e., by the development group as a whole.
I encourage others to commit to the FAQ.html file in CVS. The only
unique thing I do is to generate
Christopher Browne wrote:
[EMAIL PROTECTED] (Bruce Momjian) writes:
The worst was my upstairs hallway that had no light fixtures, so late at
night if no other lights were on in the house, you had to walk down the
hallway with your hands out in front of you so you didn't bump into
anything
is a sequence generated unique value. So in Oracle system
generated names are very opaque. I never saw this as a problem, since
if you wanted a non-opaque name you could always assign one yourself.
What, no dollar signs? :-)
--
Bruce Momjian| http
developer (possibly two) to
work on it for 320 hours.
I am on it! I will talk to Joshua's guys every day if I can. I am going
over the emails now that need attention.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
.
I could do it, but I am not looking for additional work. I will
continue to maintain the ordinary TODO list until we decide the bug
system is going to work.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life
at 11:37:32AM -0400, Bruce Momjian wrote:
It is time for people to report their port testing. Please test against
current CVS or beta5 and report your 'uname -a'.
I need this small patch so it properly detects I have unix domain
sockets. Otherwise no problems.
Kurt
[ Attachment
, without messing up with the postgres code.
e.g. force the PostgreSQL to write to stable storage after an INSERT
command.
For stable storage, you mean disk storage? You need fsync for that,
probably, but we already fsync our write-ahead log (WAL) on every
commit.
--
Bruce Momjian
I just tested gcc 2.95.3 on BSD/OS i386 and didn't see any change when
using -g3 vs -g in the size of the binaries.
---
Neil Conway wrote:
On Sat, 2003-10-25 at 21:29, Bruce Momjian wrote:
configure --enable-debug
on exit of the thread the postmaster blows up.
Before we get into details is there any obvious reason postgres doesn't like
to deal with threads?
Yes, the backend code is not thread-safe.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your
/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
---(end of broadcast)---
TIP 8: explain analyze is your friend
--
Bruce Momjian| http://candle.pha.pa.us
?
--
Tatsuo Ishii
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end
Kurt Roeckx wrote:
On Thu, Oct 30, 2003 at 11:59:05PM -0500, Bruce Momjian wrote:
OK, I have committed changes to release.sgml so most complex entries
have a paragraph describing the change. You can see the result at:
* Full support for IPv6 connections and IPv6 address data types
Joe Conway wrote:
Bruce Momjian wrote:
http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-7-4
I need people to check this and help me with the items marked 'bjm'. I
am confused about the proper text for those sections.
Allow polymorphic SQL functions (Joe
tree doesn't do the inlining, only the optimizer.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square
);
break;
case T_String:
default:
n = makeStringConst(v-val.str, NULL);
break;
}
return n;
}
which uses makeStringConst().
--
Bruce Momjian
)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL
it can't hurt ---
it changes failed queries for those that do initdb.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown
: RERERENCES
I now see the question Tom had was wether we force an initdb. Seems
this query select * from information_schema.tables; is broken without
it. I think we should fix it but not force an initdb ---
information_schema is new and I am not sure how many people are using
it.
--
Bruce
could pass it a list of
our files and it would do all of them optimally.
From what I have heard so far, sync() still seems like the most
efficient method. I know it only schedules write, but with a sleep
after it, it seems like maybe the best bet.
--
Bruce Momjian| http
what big benefit do we get by having someone
else write into the kernel buffer cache, except allowing a central place
to fsync, and is it worth it considering that it might be impossible to
configure a system where the writer process can keep up with all the
backends?
--
Bruce Momjian
file.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end
. #
#== [EMAIL PROTECTED] #
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
--
Bruce Momjian
tuning here.
I know the BSD's have trickle sync --- if we write the dirty buffers to
kernel buffers many seconds before our checkpoint, the kernel might
right them to disk for use and sync() will not need to do it.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL
do control our
own buffer cache replacement strategy.
Looking at the advantages/disadvantages, a large shared buffer cache
looks pretty good to me.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard
Jan Wieck wrote:
Bruce Momjian wrote:
Now, O_SYNC is going to force every write to the disk. If we have a
transaction that has to write lots of buffers (has to write them to
reuse the shared buffer)
So make the background writer/checkpointer keeping the LRU head clean. I
explained
Jan Wieck wrote:
Bruce Momjian wrote:
I would be interested to know if you have the background write process
writing old dirty buffers to kernel buffers continually if the sync()
load is diminished. What this does is to push more dirty buffers into
the kernel cache in hopes the OS
the only question was whether _flushall() fsync file descriptors
that have been closed. Perhaps SRA keeps the file descriptors open
until after the checkpoint, or does it fsync closed files with dirty
buffers. Tatsuo?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Now, if we are sure that writes will happen only in the checkpoint
process, O_SYNC would be OK, I guess, but will we ever be sure of that?
This is a performance issue, not a correctness issue. It's okay for
backends to wait
Jan Wieck wrote:
Bruce Momjian wrote:
Tom Lane wrote:
Andrew Sullivan [EMAIL PROTECTED] writes:
On Sun, Nov 02, 2003 at 01:00:35PM -0500, Tom Lane wrote:
real traction we'd have to go back to the take over most of RAM for
shared buffers approach, which we already know to have
. This is good, no question. The bigger
question is removing sync() and using fsync() or O_SYNC for every write
--- if we do that, the backends doing private write will have to fsync
their writes too, meaning if the checkpointer can't keep up, we now have
backends doing slow writes too.
--
Bruce
Jan Wieck wrote:
Bruce Momjian wrote:
Jan Wieck wrote:
Bruce Momjian wrote:
Now, O_SYNC is going to force every write to the disk. If we have a
transaction that has to write lots of buffers (has to write them to
reuse the shared buffer)
So make the background writer
Jan Wieck wrote:
Bruce Momjian wrote:
Jan Wieck wrote:
Bruce Momjian wrote:
I would be interested to know if you have the background write process
writing old dirty buffers to kernel buffers continually if the sync()
load is diminished. What this does is to push more dirty buffers
goffy idea would be if the OS does sync every 30 seconds to
just write() the buffers and wait 30 seconds for the OS to issue the
sync, then recycle the WAL buffers --- again, just a crazy thought.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED
really has completely random access,
then there is nothing to group.
Agreed. This might force enough stuff out to disk the checkpoint/sync()
would be OK. Jan, have you tested this?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359
Neil Conway wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Another idea --- if fsync() is slow because it can't find the dirty
buffers, use write() to write the buffers, copy the buffer to local
memory, mark it as clean, then open the file with O_SYNC and write
it again.
Yuck.
Do we
update(4). Adding fsync might
correct that.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
Neil Conway wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Another idea --- if fsync() is slow because it can't find the dirty
buffers, use write() to write the buffers, copy the buffer to local
memory, mark it as clean, then open the file with O_SYNC and write
it again.
Yuck
Jan Wieck wrote:
Bruce Momjian wrote:
Jan Wieck wrote:
If the background cleaner has to not just write() but write/fsync or
write/O_SYNC, it isn't going to be able to clean them fast enough. It
creates a bottleneck where we didn't have one before.
We are trying
Jan Wieck wrote:
Bruce Momjian wrote:
Jan Wieck wrote:
Zeugswetter Andreas SB SD wrote:
One problem with O_SYNC would be, that the OS does not group writes any
more. So the code would need to eighter do it's own sorting and grouping
(256k) or use aio, or you won't be able
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610
Bison version:
bison (GNU Bison) 1.35
TIA
.strk;
--
pallamondo.net -- take a look !
---(end of broadcast)---
TIP 8: explain analyze is your friend
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Are there further concerns with this patch?
No, just getting to it now. Sorry.
Peter didn't agree with this patch, and I have to concur with him
that the need for it is unproven.
Given that it is certainly not going into 7.4
---
Joe Conway wrote:
Bruce Momjian wrote:
http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-7-4
I need people to check this and help me with the items marked 'bjm'. I
am confused about the proper text
-hackers/2002-11/msg00679.php
http://archives.postgresql.org/pgsql-hackers/2002-11/msg00512.php
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
--
Bruce Momjian
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end of broadcast
for reporting successful ports? --Bob
Right here. I just need uname -a from both machines.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup
the
buffers to disk fast enough. I think the final solution will be to use
fsync or O_SYNC.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your
Jan Wieck wrote:
Bruce Momjian wrote:
Kurt Roeckx wrote:
On Thu, Nov 13, 2003 at 04:35:31PM -0500, Jan Wieck wrote:
For sure the sync() needs to be replaced by the discussed fsync() of
recently written files. And I think the algorithm how much and how often
to flush can
Kurt Roeckx wrote:
On Thu, Nov 13, 2003 at 05:39:32PM -0500, Bruce Momjian wrote:
Jan Wieck wrote:
Bruce Momjian wrote:
He found that write() itself didn't encourage the kernel to write the
buffers to disk fast enough. I think the final solution will be to use
fsync or O_SYNC
outline? Or do we have any better proposals?
Agreed. Background write() is a win on all all OS's. It is just the
kernel to disk part we will have to have configurable, I think.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
will
not be using initdb.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
Peter Eisentraut wrote:
Bruce Momjian writes:
Oh, I forgot about that. This leaves datetime.h and decimal.h in
/pgsql/include. I don't see how 7.4.1 can fix that because people will
not be using initdb.
This has nothing to do with initdb.
Right. I mean install isn't going to remove
pretty safe to apply, and I'm not 100% sure I still have a
local copy of the patch, so I can't let it drift too much :(
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
--
Bruce Momjian
It is not on by default?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
writes for data files, I think this could
work.
fsync() doesn't return until the data is on the disk. It doesn't
schedule the write then return, as far as I know. sync() does schedule
the writes, I think, which can be bad, but we delay a little to wait for
it to complete.
--
Bruce Momjian
value to this and would encourage people to play
with something that probably is is of little value.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can
fix, or hold this
for 7.4.1?
Must fix, I believe, especially if it is the same function call sequence
used by the postmaster so we have a high probability it will work on all
platforms.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610
this to 7.4?
I guess the question is whether we would fix this in a minor release,
and I think the answer it yes, so we can fix it now.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13
comparisons)
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your
Jan Wieck wrote:
Bruce Momjian wrote:
Our philosophy has never been to give people configuration options just
in case they might be valuable to them. If we did that, we would be
like Oracle.
We give config options only if we can't decide the best default. For
testing, you can
please check CVS HEAD. Tom has just applied the patch fix
this and we could use more testers.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your
licensing has made it
abundantly clear. MySQL just isn't in the same league, and probably
will never be. What people want is Informix/Oracle/MS-SQL = PostgreSQL.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life
projects.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
---(end
();
+ }
/* Create required subdirectories */
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
darnit!
patch attached.
Applied with correction (you got the return-value check backwards)
and further work to deal reasonably with error conditions occurring
in check_data_dir.
Tom applied it before I could.
--
Bruce Momjian
for the buck in creating the background writer.
Better Journalistic Manipulator == BJM. :-)
_B_ruce _J_. _M_omjian.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ
pretty arbitrary to me. I can't
think of any time-based interface that has that API. And what if a
trigger called now() in an earlier query and you didn't even know about
it.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Where am I wrong?
I don't think any of this is relevant. There are a certain number of
blocks we have to get down to disk before we can declare a transaction
committed, and there are a certain number that we have to get down to
disk
or just the buffers it
wrote.
I think this is these are the basics of the current discussion.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your
Hannu Krosing wrote:
Bruce Momjian kirjutas E, 17.11.2003 kell 02:31:
Defining now() as the first call seems pretty arbitrary to me. I can't
think of any time-based interface that has that API. And what if a
trigger called now() in an earlier query and you didn't even know about
Tommi Maekitalo wrote:
Hi,
in doc/man1/psql.1 there is a line:
Welcome to psql 7.4beta5, the PostgreSQL interactive terminal.
Yea, sorry. It pulls the version number from the time those man pages
were built. Not sure how we could have prevented it.
--
Bruce Momjian
. If we don't get that working you might want to use the 1000
gap idea because it doesn't cause this problem, and we don't support
1600 columns, so a 1000 gap shouldn't cause a problem and can be
modified later. If they hit 999 updates, just tell them to dump/reload
the table.
--
Bruce Momjian
a nifty feature.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup.| Newtown Square, Pennsylvania 19073
library.
Oh, seems like a TODO here. We already know how to do thread locking in
port/thread.c so maybe we just need to add some locks in there.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard
?
We stopped crashing in 7.0, or was it 6.5 --- that was our milestone, I
think. :-)
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup
idea. It would require a lot of code renaming in the
backend, but it could be done.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup
1 - 100 of 16619 matches
Mail list logo
