German_Germany" rather than "de_DE".
Yep. I have improved the documentation with the attached patch.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your
someone, can we get feedback on the patch at this URL?
http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard dri
clear from the comments why this change was needed, but if someone
> could change mybuf back to 8192 bytes (or something significantly more than
> MAX_PATH+1 (which on windows is only 260)) - I think it would be a good
> thing?
> Regards,
> Bob
>
> --
> Sent via pgsql-bugs m
ted running Postgres 7.3 and we have improved SSL
quite a bit since then so perhaps an upgrade and reading the current
docs would help the user.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If y
me, "Bear",
disappeared, and our code required SSL certificates at that point, so I
removed the requrement:
http://archives.postgresql.org/pgsql-hackers/2002-09/msg01522.php
I will work with Magnus on cleaning this up.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjia
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I found the reason for the patch; the SSL guy at that time, "Bear",
> > disappeared, and our code required SSL certificates at that point, so I
> > removed the requrement:
>
> Hmm, accor
foo add column f5 int;
> ALTER TABLE
> regression=# alter table foo drop column f5;
> ALTER TABLE
> regression=# create or replace rule redirect as on insert to foo do instead
> insert into foo1 values(new.*) returning foo1.*;
> ERROR: RETURNING list has too few entries
>
> which does seem lik
Hiroshi Saito wrote:
> Hi.
>
> This can obtain a comfortable result.
> http://winpg.jp/~saito/pg_work/OSSP_win32/pg8.3.3-win-bin-uuid-ossp-20080706.zip
>
> I will adjust with Rarf-san.
Has this been completed?
--
Bruce Momjian <[EMAIL PROTECTED]>http://m
r version it
> works, but the result is wrong.
> select to_date('2008-31-4','IYYY-IW-ID')
> in version 8.2.6 results in "2004-07-26", which is wrong.
Yes, we have fixed some of this in 8.3.
I have added your report to the existing TODO item.
--
Bruce M
Hiroshi Saito wrote:
> Hi.
>
> Yes, Finally Ralf-san adjusts this patch.
> http://winpg.jp/~saito/pg_work/OSSP_win32/.
> Therefore, it is contained in the next release.(1.6.3/4)
OK, good. Does any of this get applied to contrib/uuid-ossp?
--
Bruce Momjian <[EMAIL PROTE
olled by "client_encoding".
>
>
> it would be usefull to always see the sql statement that provoked the error.
> especially in the case of wrong utf byte sequences it can get very difficult
> to find the point of failure without more information.
I am unclear what would cau
but I think we need to move the main FAQ to a wiki at some
point.
--
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-
working
> without implementing a pretty complete XPath parser. We need to find
> another way.
>
> regards, tom lane
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> htt
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Is there any TODO here?
>
> It's clearly broken, if that's what you mean. I don't know enough XPath
> to speculate about an appropriate fix.
The XML wiki already had bug reports abo
ely user-defined
> object? "CREATE SCHEMA version" perhaps ...
I have added a comment in the source code about this.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a h
t is deprecated.
Uh, we will probably never remove timeofday() but the new functions are
clearer.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your ba
e.
>
> In any case, now that we know that nLocks overflow is actually possible
> within real-world transaction lengths, it'd behoove us to do something
> about that in 8.4 or beyond.
Is this a TODO?
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
Ente
is an end-of-file marker on Windows.
>
> Well, why is that a bug? If the platform is so silly as to define text
> files that way, who are we to argue?
The problem is that our pg_controldata might have binary values that
contain 0x1a that will be confused by the operating system as
end-of-
or change the escape character:
test=> SELECT E'\\' LIKE E'\\' escape 'a';
?column?
--
t
(1 row)
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://ente
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Mathieu Fenniak wrote:
> >> I noticed that (SELECT E'\\' LIKE E'\\') returns false,
>
> > I believe this is caused because backslash is the default escape
> > characte
d README.HOT, patch attached.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
DROP TABLE test;
CREATE TABLE test (x int);
DROP SEQUENCE seq;
CREATE SEQ
compliant than MySQL, but
Postgres is not 100% compliant either. Is any database system 100%
compliant?
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your
gsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your lif
Bruce Momjian wrote:
>
> Thanks, fixed, sources -> source.
Oops, sorry, I did not fix it. I fixed it on developer.postgresql.org,
but that is not where ftp.postgresql.org is pointed
now
--- thanks!
---
>
> On Thu, 23 Oct 2008, Bruce Momjian wrote:
>
> > Bruce Momjian wrote:
> >>
> >> Thanks, fixed, sources -> source.
> >
> > Oops, sorry, I did not fix it. I fixed it on developer.postgresql.org,
> >
I tried this:
test=> create table test (x text, y text);
test=> copy test from '/rtmp/1' with csv;
COPY 3
where /rtmp/1 had:
"a", "b"
a, "b"
a, b
and saw no errors or warnings.
gt;lc_messages = 'C'
> >or
> >lc_messages = 'english.english'
> >
> >in freebsd i have no this bug.
>
> I have reported this bug about a month ago:
> <http://archives.postgresql.org/pgsql-bugs/2008-10/msg00026.php> b
>
> >
> > What does $(CURDIR) resolve to on mingw? Try the following makefile:
> >
> > default:
> > @echo $(shell pwd)
> > @echo $(shell pwd -W)
> > @echo $(CURDIR)
> >
> >
--
Bruce Momjian <[EMAIL PROTECTE
at didn't look at the same info as the current code?
>
> Anyway the patch mentioned at the start of the thread
> http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php
> purports to fix this. It doesn't seem to have gotten reviewed
> though.
Where are we on this
posting on the topic, I think. Status?
---
>
> Regards,
> Gevik.
>
>
> > -Original Message-
> > From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, August 05, 2008 4:54 PM
> > To: Bruce Momjian
> > Cc: Tom Lan
t; functions, with potentially nasty consequences if they chanced to be
> > security definers.
>
> Is this actually true or did we just forget it? :-)
Did we ever address this?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterpri
> The short answer is "don't hold your breath". It'd be nice to have a
> plan for improving things though.
Is this a TODO?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard dr
ot;, tmp, i, last_dot + 1);
> free(tmp);
> return s;
> }
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
--
Bruce Momjian http:
ld, for consistency.
>
> Kev
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
--
Bruce Momjian http://momjian.us
EnterpriseDB http
> (3 rows)
> >
> > Since GET DIAGNOSTICS is documented as working for every SQL query
> > executed in the function, rather than for a specific list of
> > constructs, this is clearly a bug.
> >
> > --
> > Andrew (irc:RhodiumToad)
> >
> > --
> >
.UTF-8
> (1 row)
>
> dimpact=# select totaalbedragaanslag from import.aanslag;
> totaalbedragaanslag
> -
>33.33
> (1 row)
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
Mark Hayen wrote:
> He Bruce,
>
> Thank you for replying.
> Does this mean that there is no way to do a "\copy from" using CSV files
> containing decimals with
> a comma?
That is correct, sorry.
--
Bruce Momjian http://momjian.us
EnterpriseDB
gt; But it seems to me to be at least as plausible that you should get
> nothing as that you should get a space for a removed tag.
>
> Comments?
>
> regards, tom lane
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make cha
hat we should
> also backport.
>
> Regards,
>
> --
> Fujii Masao
> NIPPON TELEGRAPH AND TELEPHONE CORPORATION
> NTT Open Source Software Center
[ Attachment, skipping... ]
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To mak
ystem_ll_cc.affix, that would still work for
> > me.
>
> Right, so I changed the patch accordingly.
>
> Thanks,
>
> Martin
> --
> Martin Pitt| http://www.piware.de
> Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian
blah
> (1 row)
>
> But it seems to me to be at least as plausible that you should get
> nothing as that you should get a space for a removed tag.
>
> Comments?
>
> regards, tom lane
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgr
t; I agree. It might have been better to define it the other way
> > originally, but the risks of changing it now outweigh any likely
> > benefit.
>
> Agreed. It's too confusing the other way.
>
> The manual entry wasn't changed from my original submission
> u
Attached is a patch against HEAD. I think that we should
> also backport.
>
> Regards,
>
> --
> Fujii Masao
> NIPPON TELEGRAPH AND TELEPHONE CORPORATION
> NTT Open Source Software Center
[ Attachment, skipping... ]
>
> --
> Sent via pgsql-bugs mailing list (pgs
vice pack 3.
Hmmm. Please try specifying the file name with psql -f, rather than <.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-bug
Robert Haas wrote:
> > 2009/1/10 Tom Lane :
> >> Bruce Momjian writes:
> >>> Uh, is this ready to be applied?
> >>
> >> I don't think any consensus has been reached on changing this behavior.
> >
> > I thing, so this is bug - RETU
> (3 rows)
> >
> > Since GET DIAGNOSTICS is documented as working for every SQL query
> > executed in the function, rather than for a specific list of
> > constructs, this is clearly a bug.
> >
> > --
> > Andrew (irc:RhodiumToad)
> >
> > --
e it was issued in February, and the
> rest of the thread was posted in January. Is there any way to make the
> mailing list archives link these messages back to the rest of the
> thread?
I am tracking this item and was waiting for someone to reply to it.
--
Bruce Momjian
until i found the link above.
So what changes do you suggest?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-bugs mailing list (pgsql-bugs@post
> What is this? How can I repair this?
Our TODO list has this:
Diagnose problem where shared memory can sometimes not be attached by
postmaster children
* FATAL: could not reattach to shared memory (Win32)
http://archives.postgresql.org/pgsql-gen
l)
> Setting statement_timeout in postgresql.conf is not recommended because it
> affects all sessions.
> **Need a job? Find employment help in your area.
> (http://yellowpages.aol.com/search?query=employment_agencies&ncid=emlcntusyelp0005)
See also ALTER US
protocol. That has got to be deprecated
> enough to not worry about :-). Then again, it wouldn't be hard to put
> set ImmediateInterruptOK there as well, for the sake of completeness.
>
> --
>Heikki Linnakangas
>EnterpriseDB http://www.enterprisedb.com
--
Bru
ng up
> other order dependant code.
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
--
Bruce Momjian http://momjian.us
EnterpriseDB htt
owsers do, so I think Magnus patterned the libpq behavior
around cases where warning/prompt failed in these environments.
I am not saying the current behavior is correct, only why it was
configured that way.
--
Bruce Momjian http://momjian.us
EnterpriseDB
e file is named %APPDATA%\postgresql\root.crt.) libpq will
then verify that the server's certificate is signed by one of the
trusted certificate authorities. The SSL connection will fail if the
server does not present a trusted certificate.
I will now look at improvin
Type "help" for help.
I had to add a second error message line; I didn't see us doing a
second line anywhere else in libpq, but it seemed to be the only
solution. Should I use three lines?
--
Bruce Momjian http://momjian.u
if there is no root.crt
file. The only other approach would be to add an sslverify value of
'try' that tries only if root.crt exists.
A separate issue is if sslverify should default to 'cn'.
--
Bruce Momjian http://momjian.us
EnterpriseDB
on".
l1 and 0O where taken? ;-)
It would be nice if 'sslverify' mimicked 'sslmode', which has these
values:
disable
allow
prefer
require
I don't see how we could use 'allow', but 'disable', 'prefer', and
Bruce Momjian wrote:
> It would be nice if 'sslverify' mimicked 'sslmode', which has these
> values:
>
> disable
> allow
> prefer
> require
>
> I don't see how we could use 'allow', but 'disable',
e is just too much risk of misconfiguration with two parameters.
I would actually call the two parameters 'verify-cert' and 'verify-cn',
and document that they also have "require" behavior. Obviously you
can't verify certificates unless you require SSL.
I am fine wit
ify. Or they could be "require-no-cn"
> and "require-no-cert" perhaps?
>
> ("default choice" only for those using ssl of course - we'd still have
> "disable" as the default *value* of the parameter)
I think the "no" options are
Magnus Hagander wrote:
> On 14 apr 2009, at 04.33, Bruce Momjian wrote:
>
> > Magnus Hagander wrote:
> >>> I would actually call the two parameters 'verify-cert' and 'verify-
> >>> cn',
> >>> and document that they also hav
Applied. Depending on how we handle this the error text might need to
change but odds are we will still need to report something related to
sslmode/sslverify when root.crt is missing.
---
Bruce Momjian wrote:
> Pe
Bruce Momjian wrote:
> > That's the intention. When you're turning off something, I think it
> > makes sense to use "no"
>
> But that doesn't scale: sslmode currently has four options, soon
> perhaps to be six. The idea is that the items shou
# encoding
>
> # These settings are initialized by initdb, but they can be changed.
> lc_messages = 'C'# locale for system error message
> # strings
> lc_monetary = 'C'# locale for monetary formatting
&
.
>
>
> How can I know when a fix will be released ?
Uh, have you tried rebooting the server? Here is our TODO item:
Diagnose problem where shared memory can sometimes not be attached by
postmaster children
* FATAL: could not reattach to shared mem
Bruce Momjian wrote:
> Ghislain ROUVIGNAC wrote:
> > Thanks for your answer.
> >
> >
> > Stoping/starting the server does not solve the problem.
> > It reappears quickly.
> >
> > As a work around I still run my DB on Linux Red Hat with Postgres
Ghislain ROUVIGNAC wrote:
> I didn't tried to reboot the windows server.
> I'll try it when i will have time.
>
>
> Thank you for the references to the problem.
OK, let us know if it does not fix the problem. As you can see this
bug has been around for a wh
on IM now but I am hoping one
of our Win32 guys has an idea.
I am moving this email over to the bugs list. Folks, here is a history
of the bug report; it seems he can't install in /data on Windows:
http://archives.postgresql.org//pgsql-novice/2009-04/msg00079.php
--
Bruce Momjian
are from log_statement = all. The output of
log_min_duration_statement would be showing you times as well as
queries. The two settings do not control each other.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard
tion result type. I'm not too sure about how
> hard this is to fix, but in the meantime you will need to dump and
> recreate/reload that particular table in order to get it to work.
Is this a TODO?
--
Bruce Momjian http://momjian.us
EnterpriseDB
around with, the following, but it is really a kludge.
>
> WHERE
>g.box_boundary @> box( w.geocode, w.geocode ) and
>g.boundary @> w.geocode;
This is already mentioned on the TODO list:
Add missing operators for geometric data types
Some geometric types do not
ook at share/postgresql.conf.sample you will see that line too.
I think you need to look elsewhere about how that got set to '%%t'; I
have no idea.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life i
# special values:
so I am unclear why Windows would have a different default. How are you
viewing this default? From the command line?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard dri
(although that specifically disallows the ordering "oxf" that you
> suggest) and I see it in tar on HPUX 10.20, which ought to be about
> ancient enough for anybody.
My old BSD has:
-o Write very old style tar archive, omitting the storage of direc-
to
;
> You are entirely correct, it was the Debian init scripts trying to
> parse the config file. My apologies for wasting your time. I should
> have confirmed where the error message came from.
Debian has frustrated us in the past with their imperfect modifications
to o
led right now: does anyone see a reason not
> > to fix that?
>
> +1 for backpatching as far as you conveniently can.
Will we be _forever_ fixing coding mistakes in formatting.c?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterpri
David Fetter wrote:
> On Mon, Jul 06, 2009 at 01:53:28PM -0400, Bruce Momjian wrote:
> > Tom Lane wrote:
> > > Heikki Linnakangas writes:
> > > > Looking at the code, that looks like an oversight and the fix is
> > > > trivial:
> > >
> >
Greg Stark wrote:
> On Mon, Jul 6, 2009 at 7:20 PM, Bruce Momjian wrote:
> > I feel like someone should take a flame-thrower to that file. ?;-)
>
> If you were half the man you used to be would you?
I thought we had flame-throwed it a couple of of times, with overhauls,
but obvi
ty tab on the Program Files folder where the
> PostgreSQL folder resides, and I have Full Control on all the permissions.
>
> Not sure why I keep getting this "Failed to set permissions on the installed
> files" error. What's going on?
>
> --
> Sent via pgsql
> The main point I can see offhand is that password checking would have
> to be done a lot later in the startup sequence, with correspondingly
> more cycles wasted to reject bad passwords.
Is this a TODO?
--
Bruce Momjian http://momjian.us
EnterpriseDB
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> Now that we have SQL-level CONNECT privilege, I wonder just how much
> >> functionality would be lost if we got rid of the flat files and told
> >> people they had to use CONNECT to do any
t; (WSH aktivatet !)
>
> Check on the TODO list and in the FAQ is negatve !
> ( Search: " An error occured executing the Microsoft VC++ runtime installer"
> and " Windows XP " )
I think this is an installer problem so you should contact EnterpriseDB,
the instal
e command and the crash text?
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to
e omitted on systems without an o_sync.
Yea, that C file needed some help. I have applied the attached patch to
CVS HEAD and 8.4.X. Thanks for the report and let me know if you think
this can be improved further.
--
Bruce Momjian http://momjian.us
EnterpriseDB
hought I knew the libc API pretty well, but I learned something new
here. :-)
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-bugs mailing list (pgsql-bugs
TE TABLE test4(col1 xx NOT NULL);
CREATE TABLE
test=> INSERT INTO test4 VALUES (ROW(NULL));
INSERT 0 1
test=> SELECT * FROM test4 WHERE col1 IS NULL;
col1
--
()
(1 row)
Here I am illustrating that NOT NULL and
re not a bug.
> The way to make it work is of course the same as for any other
> client, eg put PGHOST=/socket/directory in your environment.
Is this current TODO item incorrect? Should it be removed?
Have pg_ctl look at PGHOST in case it is a socket directory?
--
Bruce Mom
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> My current feeling about it is that setting unix_socket_directory as a
> >> configuration parameter is only useful to those who are deliberately
> >> trying to hide their postmaster from regular
nstant should be named
> something like PG_...; otherwise it looks like we are defining or
> overriding an official symbol from the GSS API.
Agreed. In my first glance at the patch I thought GSS_MAX_TOKEN_LENGTH
was defined in a system include file.
--
Bruce Momjian http://momji
than earlier. The attached patch accomplishes
this. The code still goes into interactive mode, though:
$ psql -f - test
test=>
Should that prompt not appear? Seems OK to me.
--
Bruce Momjian http://momjian.u
Applied. Thanks for the report.
---
Bruce Momjian wrote:
> Robert Haas wrote:
> > On Fri, Nov 27, 2009 at 1:42 AM, Peter Eisentraut wrote:
> > > On tor, 2009-11-26 at 22:59 -0500, Robert Haas wrote:
&
iming race
applies to all uses of access(), so it is better to attempt the operation
itself to see if it will succeed. (Processes designed to run setuid or
setgid should call seteuid(2) or setegid(2) as needed to suspend their
special privileges.)
--
Bruce Momjian
Tom Lane wrote:
> Bruce Momjian writes:
> > I think access's reputation as something to avoid caused us not to look
> > at it. My old BSD manual says about access():
>
> > CAVEAT
> > The access() function should be used rarely, if ever. Specifically,
>
ion:Password change restrictions
> Details:
>
> I would like to make an enhancement request to be able to restrict the
> amount of times a database account may have its password changed in one
> 24-hour period. Thank you.
For such a case you would need to use ldap and configur
end migrating to
> > the core XML support instead.
>
> Ok, sorry for the silly question but is the xml core support
> comparable to contrib/xml2? Is it already there in 8.4 or is scheduled
> for 8.5?
It is in 8.4 and is superior to what was supported in contrib/xml2
e this wasn't immediately clear, so I
applied the attached documentation patch.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backu
Tom Lane wrote:
> Alvaro Herrera writes:
> > Bruce Momjian escribi?:
> >> I found one place in the docs where this wasn't immediately clear, so I
> >> applied the attached documentation patch.
>
> > I liked Tom's suggestion better, because then you
s, and then ran "SELECT word FROM
pg_get_keywords() WHERE catcode != 'U'" to get all the keywords from our
C code, and then compared the two. The two missing keywords were OVER,
and WINDOW, as you mentioned.
I have applied the attached patch to CVS HEAD and 8.4.X to properly
8
> Blocks per segment of large relation: 0
> WAL block size: 0
> Bytes per WAL segment:1093850759
> Maximum length of identifiers:8192
> Maximum columns in an index: 131072
> Date/time type storage: 64-bit in
the docs so they don't say that binary distros
> will include the pre-built tutorial binaries, and then we can consider
> shipping the source files in the installers/rpms etc.
I have applied the attached patch which removes the mention that the
tutorial files are precompiled.
--
Br
1 - 100 of 1582 matches
Mail list logo
