Alvaro Herrera wrote:
Bruce Momjian wrote:
! /* print a divider, middle columns only
*/
! if ((j + 1) % col_count)
{
! if (opt_border == 0
Bruce Momjian wrote:
I think it's a bad idea to use the same : separator in the two last
cases. They are different and they should be displayed differently.
I confirmed with Alvaro that he didn't notice the first uses a colon and
the second a semicolon, so he is OK.
FYI, I added
..
If you can come up with an easily installable tarball, I can dedicate
1 or 2 boxes to run it 24/7.
Sure. I updated the script so it will be clearer what you have to
modify.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http
Bryce Nesbitt wrote:
Bruce Momjian wrote:
I don't think you need to do that to get it applied --- there is nothing
windows-specific in your code.
Is this ready to be applied? Do you want to send a final update or are
you still testing?
Looks good, but I suggest adding give up
bruce wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
The closest thing I can think of to an automated test is to run repeated
sets of the parallel regression tests, and each time SIGTERM a randomly
chosen backend at a randomly chosen time. Then see
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Attached is my test script. I ran it for 14 hours (asserts on),
running 450 regression tests, with up to seven backends killed per
regression test.
Hmm, there are something on the order of 1 SQL commands in our
regression
Magnus Hagander wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Attached is my test script. I ran it for 14 hours (asserts on),
running 450 regression tests, with up to seven backends killed per
regression test.
Hmm, there are something on the order of 1 SQL
bruce wrote:
Magnus Hagander wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Attached is my test script. I ran it for 14 hours (asserts on),
running 450 regression tests, with up to seven backends killed per
regression test.
Hmm, there are something
bruce wrote:
bruce wrote:
Magnus Hagander wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Attached is my test script. I ran it for 14 hours (asserts on),
running 450 regression tests, with up to seven backends killed per
regression test.
Hmm
Bryce Nesbitt wrote:
Bruce Momjian wrote:
I spent time reviewing your patch --- quite impressive. I have attached
and updated version with mostly stylistic changes.
In testing I found the regression tests were failing because of a divide
by zero error (fixed), and a missing case
for multibytes in there, but perhaps I'm missing it.
* } else is forbidden too. Use two separate lines.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
Alvaro Herrera wrote:
Bruce Momjian wrote:
Alvaro is correct. I made most or all of these adjustments in the
updated version I posted yesterday.
Doh. I didn't realize you had posted a new version :-(
People is complaining here that we don't teach people here anyway, so
hopefully
the option to a shorter wrapped. I added documentation too.
For testers compare:
\df
with:
\pset format wrap
\df
Impressive!
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life
Applied.
---
Bruce Momjian wrote:
oikBruce Momjian wrote:
Bruce Momjian wrote:
When we get the termination signal, why can't we just set a global
boolean, do a query cancel, and in the setjmp() code block check
code does
not contain a real capitalization function. It sucks when we have
composite names like the portuguese above. I'll post an updated version
later.
Euler, have you updated this patch yet?
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
oikBruce Momjian wrote:
Bruce Momjian wrote:
When we get the termination signal, why can't we just set a global
boolean, do a query cancel, and in the setjmp() code block check the
global and exit --- at that stage we know we have released all locks and
can exit cleanly.
I
Bruce Momjian wrote:
When we get the termination signal, why can't we just set a global
boolean, do a query cancel, and in the setjmp() code block check the
global and exit --- at that stage we know we have released all locks and
can exit cleanly.
I have implemented this idea
Bruce Momjian wrote:
I have an idea for this TODO item:
* Allow administrators to safely terminate individual sessions either
via an SQL function or SIGTERM
Lock table corruption following SIGTERM of an individual backend
has been reported in 8.0
Bruce Momjian wrote:
Bruce Momjian wrote:
I have an idea for this TODO item:
* Allow administrators to safely terminate individual sessions either
via an SQL function or SIGTERM
Lock table corruption following SIGTERM of an individual backend
has been
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
When we get the termination signal, why can't we just set a global
boolean, do a query cancel, and in the setjmp() code block check the
global and exit --- at that stage we know we have released all locks and
can exit cleanly.
I
from a variety of contributing
+Other language bindings are available from a variety of contributing
parties.
Thanks, fixed (not ignored). ;-)
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life
;
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your
project by donating at
http://www.postgresql.org/about/donate
[ Attachment, skipping... ]
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
.
[ Attachment, skipping... ]
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
--
Bruce Momjian [EMAIL
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
This has been saved for the next commit-fest:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
Er, why saved? Until there's a new patch submission there's not going
to be more work to do on this in the next fest.
I think
the
comments made too.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes
mailbox and just track
them there too. I moved them so it would be visible we were waiting for
some people.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Bruce Momjian [EMAIL PROTECTED] wrote:
Added to TODO:
o Add ability to obfuscate function bodies
For the record. I think this todo is bogus.
For the record, I think so too ;-). The agreed-on TODO wording makes no
mention
\361\214}\231\240L/\020\232\036c\234\315P\236\266I\370\324\222
proconfig |
proacl |
[ Attachment, skipping... ]
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
--
Bruce Momjian [EMAIL PROTECTED]http
rather than every year because it can break
stuff that we have to manually fix by adding includes.
If you want it run now or every year, let me know.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life
includes bufmgr.h, but bufpage.h does not require any definition
from
bufmgr.h. I think this dependency is there for long time.
My scripts should have found this issue, see
src/tools/pginclude/pgrminclude.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I run it every few years rather than every year because it can break
stuff that we have to manually fix by adding includes.
If you want it run now or every year, let me know.
I'm not in a hurry --- as we found out last time
Alvaro Herrera wrote:
Gregory Stark wrote:
Here's the WIP patch I described on -hackers to implemented ordered append
nodes.
Did you ever publish an updated version of this patch?
I don't think so. I think we just need to tell Greg if he should
continue in this direction.
--
Bruce
to \? without typing \?.
Shame we can't make \h more prominent in \? output. I am going to try
to trim down that top help section, but that will a separate patch
posting by me.
Any adjustments?
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
a
problem. unused_oids is useful to find, err, unused OIDs.
Ahh, hadn't found those, thanks. They're in the dev FAQ too, *blush*.
I need this for something I'm doing at $ork, and thought I'd
implement it in the backend, as well as a .so, it's been a learning
experience :)
--
Bruce
expanded on that and removed the mention of the web
site, which seemed odd to be just in the 'help' output. (I added a \h
mention.)
Update patch applied, that also reverses the previous patch.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
://www.postgresql.org.uk
[ Attachment, skipping... ]
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/backup.sgml
SQL/PSM stuff to Postgres will be less than impressed by
our function body as a string mechanism.
What is your point? That because of the $$ strings they might as well
rewrite the whole thing in PL/pgSQL.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
as a reason for doing this. We'd really have to suck it up and figure
some other way of parsing function bodies.
Oh, I understand now, that we aren't going to be 100% standards
compliant based on how we quote our function bodies --- I understand
Andrew's point now.
--
Bruce Momjian [EMAIL
Volkan YAZICI wrote:
Hi,
Sorry for the delay, but the reply of Tom didn't reach me. I've modified
the patch according to Tom's comments. I hope I am not too late.
OK, great. I will re-add it to the current queue and add this email as
well.
--
Bruce Momjian [EMAIL PROTECTED]http
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
to
one user just doesn't make sense. We need a plan on exactly what we
want to expose in a coherent way, and how.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your
of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ
-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard
mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive
, tom lane
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http
[ Attachment, skipping... ]
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://enterprisedb.com
Kotala wrote:
Tom Lane napsal(a):
Bruce Momjian [EMAIL PROTECTED] writes:
Where are we on this? Tom thinks we don't want this. TODO has:
* Prefix command-line utilities like createuser with 'pg_'
http://archives.postgresql.org/pgsql-hackers/2007-06/msg00025.php
I think we need
.
Committed to HEAD with minor fixes.
What's our policy wrt. back-patching doc changes? This seems applicable
to older versions as well, but do we do that?
I do backpatch of doc changes if the change is serious.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
Bruce Momjian wrote:
There are patch queue comments suggesting the removal of the ipcclean
command-line utility. ipcclean doesn't work on Windows, and it probably
doesn't work perfectly all Unixes either.
The attached patch removes the utility, though some files will have to
be removed
Hiroshi Saito wrote:
Hi.
As for windows, unnecessary garbage is processed.
Please apply it.
We have decided to remove ipcclean for all platforms so this patch is
no longer necessary.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
Alvaro Herrera wrote:
Bruce Momjian escribi?:
This has been saved for the next commit-fest:
I noticed you broke an URL that previously worked: what was
http://momjian.us/mhonarc/patches/[EMAIL PROTECTED]
is now
http://momjian.us/mhonarc/patches_hold/[EMAIL PROTECTED]
May I suggest
Alvaro Herrera wrote:
Bruce Momjian escribi?:
Alvaro Herrera wrote:
I noticed you broke an URL that previously worked: what was
http://momjian.us/mhonarc/patches/[EMAIL PROTECTED]
is now
http://momjian.us/mhonarc/patches_hold/[EMAIL PROTECTED]
May I suggest that the URLs
Alvaro Herrera wrote:
Bruce Momjian escribi?:
Alvaro Herrera wrote:
My point is that you should only _add_ Message-Ids, not remove them.
You can move the messages from one queue to the other to your heart's
content, but the Message-Id URL should continue to work with no changes
Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I have developed the attached patch with improves wording for the
pg_dump -i (ignore version) option.
I think this is going in exactly the wrong direction --- it makes
both the documentation
There are patch queue comments suggesting the removal of the ipcclean
command-line utility. ipcclean doesn't work on Windows, and it probably
doesn't work perfectly all Unixes either.
The attached patch removes the utility, though some files will have to
be removed as well.
--
Bruce Momjian
are going to have the same problem.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches
Alvaro Herrera wrote:
Bruce Momjian escribi?:
OK, I remember now. The problem wasn't symlinks but that mhonarc
generates URLs relative to the current directory. If we have message-id
files outside the directory, links like Thread Next will not work. We
could try to change those
Bruce Momjian wrote:
Alvaro Herrera wrote:
Bruce Momjian escribi?:
OK, I remember now. The problem wasn't symlinks but that mhonarc
generates URLs relative to the current directory. If we have message-id
files outside the directory, links like Thread Next will not work. We
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I have developed the attached patch with improves wording for the
pg_dump -i (ignore version) option.
I think this is going in exactly the wrong direction --- it makes
both the documentation and the warning message less scary
Brendan Jurd wrote:
On 9/29/07, Bruce Momjian [EMAIL PROTECTED] wrote:
I think we need more than one person's request to add this function.
Well, I don't expect it would get requested. Most DBAs would likely
look for the function in the docs, see it's not there and then just
implement
-gzip is not supported, skipping... ]
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
--
Bruce Momjian [EMAIL PROTECTED]http
your free space map settings
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches
free space map settings
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org
something to do lightly.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/ref/pg_dump.sgml
here,
before deciding the further course of actions.
I think it is unwise to wait on Gavin for a more complex implemention
--- we might end up with nothing for 8.4. As long as your syntax is
compatible with whatever Gavin proposed Gavin can add on to your patch
once it is applied.
--
Bruce
*/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
?
http://archives.postgresql.org
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches
://www.postgresql.org.uk
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via
mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard
,
---
ITAGAKI Takahiro
NTT Open Source Software Center
[ Attachment, skipping... ]
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
suggest that we ought to just flat rip out the non
segmenting code paths in md.c, and instead look into what segment sizes
are appropriate on different platforms.
Agreed.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http
of broadcast)---
TIP 5: don't forget to increase your free space map settings
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your
)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup
);
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your
/tools/pginclude/README).
Anybody feel like working on that?
regards, tom lane
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your
as '' null as 'abc' null as '123'
\copy: parse error at null
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Index: src/bin/psql/copy.c
apply the attached patch in the mean
time (above cleanup is probably 8.4 material anyway).
-Neil
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
it now for held ideas.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org
could throw a warning on truncation
but that seems wrong too.
I am concerned a 1mb limit is too low though. Exactly why can't we have
a higher limit? Is positional information that significant?
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
.
Does that then mean that, because of the triggers on inserts, we
will never be able to add this record?
Right now, yes, unless we figure something else out.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
I don't think that follows. A tsearch index is lossy anyway, so there's
Uh, the index is lossy but I thought it was lossy in a way that just
required additional heap accesses, not lossy in that it doesn't index
archives?
http://archives.postgresql.org
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list
... ]
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
).
Regards,
-Robert
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.orgextra=pgsql-patches
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB
this to 8.3 because it would require translation
string updates.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Index: src/backend/tsearch
that the configuration section does not mention the likely
increase in recovery time that will result from setting those parameters
higher. That needs a patch. ISTM a serious omission that should be
treated as a bug and backpatched.
Patch attached and applied, and backpatched to 8.3.X.
--
Bruce Momjian [EMAIL
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 [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http
.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your
?
http://www.postgresql.org/docs/faq
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches
@postgresql.org)
To make changes to your Subscription:
http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.orgextra=pgsql-patches
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard
value that would be likely to malfunction in subsequent
use.
Seems we never documented that chr(0) is not supported. I have applied
the following doc patch to CVS HEAD and 8.3.X.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http
: don't forget to increase your free space map settings
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list
friend
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes
datatypes do not
match
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-patches mailing list (pgsql-patches
BAndrew Dunstan wrote:
Bruce Momjian wrote:
Tom Lane wrote:
Steve Clark [EMAIL PROTECTED] writes:
I'm not sure I understand what you mean about TEXT being null-safe.
What are the issues, and why was
it supported for years and now abruptly changed.
It never
. I bought your suggestion :-)
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
[ Attachment, skipping... ]
---(end of broadcast)---
TIP 6: explain analyze is your friend
--
Bruce Momjian [EMAIL PROTECTED]http
noisy.
Possibly the REVOKE manual page could be modified to throw more stress
on the point.
Agreed, patch attached and applied.
--
Bruce Momjian [EMAIL PROTECTED]http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard
101 - 200 of 3307 matches
Mail list logo
