o one has bothered to do
anything about it yet. Feel free to propose a solution.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ch might be equally confused about this issue.
It's further complicated because you can actually run-time load the
build-time linkable file type if you try hard enough. So be sure to check
that whatever you do works with PgAccess.)
--
Peter Eisentraut [EMAIL PROTECTED]
-
returns some records.
There are probably null values in the result set of the subselect.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
stify the
confusion it causes.
--
Peter Eisentraut [EMAIL PROTECTED]
---(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 writes:
> we need someone to get MONEY working as an extented NUMERIC type.
How would the new "money" be different from "numeric"? If we have
"money", should we have "length", "mass", and "temperature"? I think not.
J
Brian Catlin writes:
> The Windows binaries for 7.3.2 are not on the FTP site. Where can I get
> them?
http://www.cygwin.com
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, pleas
,billingaddress,acctype,accnum)
values ('1',3639,FALSE,'','','',0,'PETER
CHILDS',0,1,0,30,15,'',5,0,0,'',FALSE,FALSE,FALSE,1,1,4133,3639,0,992);
COMMIT;
Output from script is
BEGIN
SET CONSTRAINTS
UPDATE 1
psql:crash:4: server clo
by tab-space
> character.
This command is parsed by the shell, so psql cannot do anything about it.
Maybe -F $'\t' works in your shell.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
th that.
I believe this design is ok, even though it creates apparent
inconsistencies. If you make it behave like you appear to imagine, then
you need to double-escape certain characters in situations where other
users might not expect it.
--
Peter Eisentraut [EMAIL PROTECTED]
---
Herrmann, DP ITS, SMN, DD writes:
> I have downloaded your PostgrSQL 7.3.1 installation for windows!
We do not distribute any Windows version of PostgreSQL. Please complain
to whomever you got it from.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadc
anded display' is turned off (in which case, however,
> the pager doesn't work!).
Perhaps the problem is that the pager does not handle the accented
characters right.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TI
ay. (I presume the statistics
don't change too much)
While I don't surgest doing a vacuum more than twice an hour as
this would slow down the system with little gain more than once a day may
improve the speed and space usage.
Just an idea.
Peter
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
ids and update it every time you took a value. (Maybe a trigger could be
used?) Due to table locking during transactions no two concurrent
requested would get the same answer. Implementation could be
interesting but relatively simple.
BEGIN;
SELECT id from unqid where name=&
Greg Sabino Mullane writes:
> Can the configure script be made to check for a proper version of bison?
Normally the parser files are prebuild and bison is never invoked. So it
seems wasteful to do a bunch of checking for this rare case.
--
Peter Eisentraut [EMAIL PROTEC
Index Cond: (a = 1)
>Filter: ((b = 1) OR (b = 2))
>
>
> Now, why doesn't it want to use the index for the second condition???
It can only use all columns of a multicolumn index if the columns are used
in clauses connected by OR. This is described in the documentation.
--
Yes, it's Sobig.E.
It seems that someone out there is infected with it and
I've had about 20 reports of this coming from me (which is funny as I
don't use M$ for email ;-) ). That's the problem with the recent virii as
they a forging the addresses :-(
Peter
--
Peter Mo
"idle in transaction" sessions, you need to fix
your application.
In 7.3 there is a system table called pg_locks that you can use to
investigate locks. I don't believe there was one in 7.2.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Nils Philippsen writes:
> Is this expected behaviour
Yes.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Nils Philippsen writes:
> On Mon, 2003-08-11 at 10:49, Peter Eisentraut wrote:
> > Nils Philippsen writes:
> >
> > > Is this expected behaviour
> >
> > Yes.
>
> Hmm. I ask myself whether this is desired behaviour, too.
No, but it will take a lot of work
$libdir/pgxml_dom' LANGUAGE c STRICT;
Yes.
See also <http://www.postgresql.org/docs/7.3/static/xfunc-c.html>.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Tommi Maekitalo writes:
> Ok - the problem I found is in psql. The help-page with LANG=de_DE (psql
> --help) lists -l twice and misses option --help. I just checked a
> 7.3.3-installation. Same problem there.
I fixed this in the 7.3 and 7.4 branches. Thanks.
--
Peter Eisentraut
lots of time. Would you please add
> this note into the documentation?
We would rather fix problems than document them. First of all, what
hangs, the server or the client? Can you find out where in the code it
hangs?
--
Peter Eisentraut [EMAIL PROTECTED]
---(e
ed.
The bug here is that the scanner doesn't know that a newline (or end of
input) is a required as part of a -- comment. If I change the rule
comment ("--"{non_newline}*)
in scan.l to
comment ("--"{non_newline}*){newline}
then the examp
[EMAIL PROTECTED] writes:
> These are the first translations of the pg_resetxlog.pot and
> pgscripts.pot files.
Installed. Please send them to pgsql-patches next time.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP
espace ({space}+|{comment}{newline})
horiz_whitespace({horiz_space}|{comment})
whitespace_with_newline ({horiz_whitespace}*{newline}{special_whitespace}*)
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the plann
t;Right" and "wrong" are defined by your system locale. Check what locale
you have set in your PostgreSQL server and whether the system locale works
as you expect. If you have further problems please post more detail,
including the locale configuration and some actual
system tables. It might be
worth a shot in this particular case, though.
> Another question is whether to force an initdb after making this change.
> If we don't, existing beta testers may continue to use the incorrect
> view definition.
I think we will have to.
--
Peter Eisentraut
RC Neil Conway has
> already been working on unique hashes, and I'm sure GIST will support it
> eventually as well.)
Isn't the whole unique index thing a dead end anyway? How are we ever
going to get deferrable unique constraints that way?
--
Peter Eis
en it can't be opened.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
FROM Fields;
> ERROR: AllocSetFree: cannot find block containing chunk 0x83a5300
Apparently, the implementation of that function contains a bug in the
memory handling.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Neha Kasat writes:
> PostGRESql doesn't convert the special characters like Å, Ò, etc into
> their lower case when using function lower and vice-versa when using
> upper.
It does if you select the right locale.
--
Peter Eisentraut [EMAIL PROTECTED]
f verbose mode, where
it prints out the commands it executes internally? I suspect that the
addition of the -pthread option results in side effects that interfere
with the -h option.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
times, but I haven't found a system yet. If you just want
to get going, edit src/template/solaris and replace -pthread by the right
option (-mt in your case?).
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe a
files. Generally, it's also unwise to rely in this kind of
subtle side effect. We need a general solution.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if
toconf tools.
Admittedly, you're not supposed to install the generated config.h files,
because of this kind of name conflict. There is a contributed macro that
automatically prefixes all macro names so they don't conflict. May be
worth checking out.
--
Peter Eisentraut [EMAI
Olleg writes:
> > because of this kind of name conflict. There is a contributed macro that
> > automatically prefixes all macro names so they don't conflict. May be
> > worth checking out.
>
> ??? Please explain.
http://ac-archive.sourceforge.net/guidod/ax_prefix_config_h.html
---
David Fetter wrote:
> Kind people,
>
> I have a little puzzlement. In the first select, I double the
> backslash and return true. In the second, I don't and get false.
> Have I missed something important in the docs?
Yes:
"""
Note: Remember that the backslash (\) already has a special meaning i
Claus Colloseus wrote:
> After creating a domain of type bit(n), the length n is given back
> with another number from the information schema.
Will be fixed in 7.4.1.
---(end of broadcast)---
TIP 7: don't forget to increase your free space map sett
gerard manvu wrote:
> I don't know if it is really a bug or a missuse of postgresql but
> when I issue the following request select decode(encode('µ'::bytea,
> 'escape'), 'escape');
> , the result is \346, not 'µ'.
That's the same thing. bytea stores bytes, not characters, so we expect
that you a
Dario Marini wrote:
> My postmaster.pid is something like:
>
> 23479
> /export/home1/staff/marini/pgsql/data
> 5432001 11703
>
> I don't know if there is something wrong with my installation (I run
> postgresql on Ultra-2 station with Solaris 6), for sure I cannot stop
> postgrsql server usin
I think the bugs entered through the web form should set headers to
allow responding to the user more easily. Right now you have to copy
the email address into the reply mail manually.
---(end of broadcast)---
TIP 3: if posting/reading through Us
Tom Lane wrote:
> If the view were also supposed to show referenced columns, then I
> think we'd need an additional UNION arm that joined on confrelid and
> confkey[] instead of conrelid/conkey[]. But if I read SQL99
> correctly, only referencing not referenced columns are supposed to be
> shown.
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> But if I read SQL99 correctly, only referencing not referenced
> >> columns are supposed to be shown.
> >
> > It is supposed to show the referenced (primary
Lauris Buk¨is wrote:
> I have PostgreSQL 7.3.2 on Mandrake 9.1.
> functions lower and upper doesn't convert UTF8 char cases... it just
> leave them as thay are. Atleast I have problems with latvian and
> russian letters. Database charset is set to UNICODE.
Yes, next time please search the archives
Lewis Foti wrote:
> I have a schema which includes one table with a CHECK constraint.
> After the schema is dumped (with pg_dump) as ascii text attempts to
> recreate it using the psql -f command cause this one
> table, called navigaion, to fail to create. This is using postgresql
> 7.3.3 on Redha
Lewis Foti wrote:
> Further to my original message I realise that the problem was due to
> the text of the rule still referring to columns, src_section_id and
> dst_section_id by their original names, parent_section_id and
> child_section_id respectively. So the nature of the bug changes to
> that
> "make install" fails on cygwin for pgtclsh:
>
> in src/bin/pgtclsh/Makefile, add $(X) to the end of every occurrence of
> 'pgtclsh' and 'pgtksh' as part of a command.
>
> Example:
> $(INSTALL_PROGRAM) pgtclsh$(X) $(DESTDIR)$(bindir)/pgtclsh$(X)
Fixed.
---(end of broadca
> In src/interfaces/libpgtcl/Makefile:
> Change:
> SHLIB_LINK = $(libpq)
> To:
> SHLIB_LINK = $(TCL_LIB_SPEC) $(libpq)
This is already fixed in 7.4.
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
> In src/pl/tcl/Makefile:
> Change:
> # link command for a shared lib must NOT mention shared libs it uses
> SHLIB_LINK = $(TCL_LIB_SPEC)
> To:
> # link command for a shared lib must NOT mention shared libs it uses
> SHLIB_LINK = $(BE_DLLLIBS) $(TCL_LIB_SPEC)
This is already fixed in 7.4.
--
> In src/pl/tcl/pltcl.c:
> Permute the order of:
> #include "postgres.h"
> #include
> so as it appears as:
> #include
> #include "postgres.h"
I' afraid this is not a fix but just paints over the symptoms. As you
noticed, this topic has already been discussed, and the solution needs to be
Gustavo Scotti writes:
> when the key is bigint, it ignores any kind of index scan, it always use
> Seq scan. Why?
RTFM: http://www.postgresql.org/docs/7.4/static/datatype.html#DATATYPE-INT
Please don't post to pgsql-bugs unless you have found a bug.
---(end of broadcast
[EMAIL PROTECTED] writes:
> In more research in this problem I found that if the
> EXEC SQL OPEN cursor; command was not present that
> ecpg would just comment out the cusrsor declare statements.
Please use a recent version and give us a reproduceable example if you expect
any kind of feedback.
Oliver Elphick wrote:
> I can't very easily get cvs tip built on linus-hppa, because I
> couldn't make a package of that except for experimental, but
> experimental doesn't get processed by the autobuilders.
Time to break out the old configure; make; make install...
---(e
Jason Tishler wrote:
> PostgreSQL-7.4.1 fails the rules regression test with a diff such as
> the one posted to the pgsql-cygwin mailing list:
>
> http://archives.postgresql.org/pgsql-cygwin/2003-12/msg00088.php
>
> Note that I *cannot* reproduce this problem under PostgreSQL 7.4.
I think thi
Denis N. Stepanov wrote:
> snprintf()/vsnprintf() functions are not ANSI-compliant
Yes, they are.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Jari Aalto wrote:
> Thank you. That did it. May I suggest adding this:
>
>
> --- INSTALL.old 2004-01-17 13:34:22.0 +0200
> +++ INSTALL 2004-01-17 13:33:32.0 +0200
> @@ -15,6 +15,7 @@
>mkdir /usr/local/pgsql/data
>chown postgres /usr/local/pgsql/data
>su - postgre
PostgreSQL Bugs List wrote:
> Entering CTRL+ALT+\ (backslash) causes psql to dump core:
That is the very purpose of that key combination. The shell sends a
SIGQUIT signal to the program, causing it to quit and dump core. You
may find that quite a lot of programs dump core that way. If you don
Philipp Matthias Hahn wrote:
> # SELECT round(5.5::float4),round(50.5::float4);
> round | round
> ---+---
> 6 |50
> (1 row)
>
> I think this is a bug, since I would expect 6 and 51.
The default rounding mode for floating point (determined by your C
library, mostly) it to round
Gary WAN wrote:
> I would like to ask if there is any SQL command to replace "CREATE
> ASSERTION" in Postgresql since ASSERTION is not supported by
> postgresql. Thank you.
There is not, but this is the wrong list to be asking this.
---(end of broadcast)
PostgreSQL Bugs List wrote:
> /usr/bin/ld -r -o SUBSYS.o heaptuple.o indextuple.o indexvalid.o
> printtup.o scankey.o tupdesc.o
> /usr/bin/ld: Relocatable linking with relocations from format
> elf64-sparc (heaptuple.o) to format elf32-sparc (SUBSYS.o) is not
> supported
You need to run
$ sparc32
PostgreSQL Bugs List wrote:
> CREATE FUNCTION test1 (int) RETURNS int LANGUAGE sql
> AS 'not even SQL';
> ERROR: syntax error at or near "not" at character 1
>
> You may notice that word "not" is not at character 1,
> where there is "CREATE".
The error message refers to the function body, whi
Tom Lane wrote:
> Looking at the code, this seems to be intentional, because the
> privilege check is not made for revokes only for grants:
> Peter, do you remember why you did it that way?
I'm not really sure right now. It doesn't really make sense, does it?
Certainl
rahul wrote:
> An old version of the database format was found.\nYou need to upgrade
> the data format before using PostgreSQL.\nSee
> /usr/share/doc/postgresql-7.4/README.rpm-dist for more information.
>
> could u please let me know, how to get rid of this problem.
Follow the instructions in
/u
Johan Duflost wrote:
> I installed mapserver a cgi using libpq client library under win2K
> within tomcat. I tried to display postgis layers stored on another
> host but I got the error message "unknown host name". I don't have
> any skill in C programming. Could you tell me how I have to patch
> f
Martin Pitt wrote:
> A week ago we at Debian received the bug report below: due to a
> buffer overflow in psqlodbc it is possible to crash (and possibly
> exploit) apache. I already sent this mail to the psqlodbc list [1],
> but unfortunately got no response so far. So maybe there are some
> hacker
PostgreSQL Bugs List wrote:
> Description:server includes not installed by default
make install-all-headers
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMA
Am Mittwoch, 12. Mai 2004 15:41 schrieb Fabien COELHO:
> > make install-all-headers
>
> Good, but not enough?
>
> I still argue that it should be done "by default"
I agree, but this is not a bug, it is a deliberate design decision. If you
want to change it, argue about it on -hackers.
-
Am Donnerstag, 6. Mai 2004 18:30 schrieb Tom Lane:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > ./configure LDFLAGS="-R /usr/local/lib" --with-tcl
> > An easier way would be to append the value of LDFLAGS to the linker
> > commands building the shared libraries, not only to those buil
Martin Pitt wrote:
> The problem is that make_string() in misc.c does not check whether
> the target buffer is big enough to hold the copied string.
>
> I added a bufsize parameter to make_string() and used it in all calls
> to it. I tried it with my php4 crash test script and now it works
> proper
Tom Lane wrote:
> After that, you get to the General Rules, which pretty clearly say
> that trying to grant privileges you don't have grant option for is
> just a warning and not an error condition. (Such privileges will not
> be in the set of "identified privilege descriptors".)
>
> AFAICS the sp
Am Freitag, 14. Mai 2004 09:25 schrieb PostgreSQL Bugs List:
> Even though PostgreSQl 7.3 installation does have a directory
> src/interface/python/ with the files pg.py and pgdb.py, version 7.4 does
> not! This prevents a (very useful) working Python interface for version
> 7.4! Was it deliberatel
Markus Bertheau wrote:
> oocms=# select 'Ñ' ~ '^\\w$';
> ?column?
> --
> f
> (1 ÑÑ)
What locale are you using for LC_COLLATE? If it's C or POSIX, you need
to change it and re-initdb.
---(end of broadcast)---
TIP 5: Have you checked
Am Donnerstag, 1. Juli 2004 23:10 schrieb Tom Lane:
> Right. The reason PG doesn't error is that we have an implicit cast
> from integer to text. I've opined before that we should mark most
> cross-type-category casts as explicit-only ... they are just too prone
> to give unexpected answers, as i
Am Freitag, 2. Juli 2004 13:20 schrieb Ilir Gashi:
> CREATE TABLE TEST(ID INTEGER,NAME VARCHAR(50));
> INSERT INTO TEST (ID) VALUES (1);
> GRANT UPDATE ON TEST TO TESTUSER;
> Connect as TestUser;
> UPDATE TEST SET NAME='TEST' WHERE ID=1;
> ERROR: test: Permission denied.
> UPDATE TEST SET NAME='TE
Me wrote:
> Am Freitag, 2. Juli 2004 13:20 schrieb Ilir Gashi:
> > CREATE TABLE TEST(ID INTEGER,NAME VARCHAR(50));
> > INSERT INTO TEST (ID) VALUES (1);
> > GRANT UPDATE ON TEST TO TESTUSER;
> > Connect as TestUser;
> > UPDATE TEST SET NAME='TEST' WHERE ID=1;
> > ERROR: test: Permission denied.
>
Am Mittwoch, 7. Juli 2004 14:58 schrieb PostgreSQL Bugs List:
> Description:evaluation order of select seems to be wrong
Please read this:
http://www.postgresql.org/docs/7.4/static/sql-expressions.html#SYNTAX-EXPRESS-EVAL
---(end of broadcast)-
David Newall wrote:
> PostgreSQL version: 7.4.3 (RPMs from ftp.au.postgresql.org)
>
> Operating Sysem: Fedora Core 1
>
> CREATE TABLE t(i integer UNIQUE);
> INSERT INTO t VALUES (null);
> INSERT INTO t VALUES (null);
> SELECT coalesce(i,-999) FROM t;
> coalesce
> --
> -999
> -99
David Newall wrote:
> PostgreSQL version: 7.4.3 (RPMs from ftp.au.postgresql.org)
>
> Operating Sysem: Fedora Core 1
>
> CREATE TABLE t1 (i INTEGER, j INTEGER);
> INSERT INTO t1 VALUES (1, NULL);
> CREATE TABLE t2 AS SELECT * FROM t1;
> SELECT * FROM t1 JOIN t2 USING (i, j);
> i | j
> ---+---
> (
Pavel Stehule wrote:
> its not error. Only SQL specific :-) NULL <> NULL
Au contraire, neither
NULL = NULL
nor
NULL <> NULL
is true.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Dana Hudes wrote:
> The documentation clearly states in section "1.1.1 Identifiers and
> Keywords" that "Identifier and key word names are case insensitive".
> It goes on to give an example where a column name is used in lower
> case and in upper case or any mixture.
>
> I have found that the actua
test
> Table "public.test"
> Column | Type | Modifiers
> +--+---
> Check constraints:
> "test2" CHECK ('\\'::text = ''::text)
It prints the SQL source code for the check constraint. There is no
bug, AFAICS.
--
Pe
Please provide a concrete, reproducible example.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(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
-d and I have a serious problem.
Maybe the clock on your system is not properly operating?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
L PROTECTED]) is the
right place.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
a KOI8-R
> locale. Then:
>
> CREATE DATABASE bug WITH ENCODING='unicode';
That's your problem. Your locale doesn't match your encoding. You need to
use a compatible combination.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
-
nd you are actually passing UTF-8 strings, the results are
going to be close to comparing garbage.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Hans Schou wrote:
> I needed to have 36 function parameters.
> PostgreSQL only allows 32.
If you index more than three or four columns you're doing something
wrong. Please explain in more detail why a practical application would
need that many index columns.
--
Peter Eise
ing about it. If
that happens, the ordering can be incorrect.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregi
/src/include -c -o initdb.o initdb.c
> initdb.c: In function `get_encoding_from_locale':
> initdb.c:744: `CODESET' undeclared (first use in this function)
> initdb.c:744: (Each undeclared identifier is reported only once
> initdb.c:744: for each function it appea
Tom Lane wrote:
> Peter, any thoughts on this one way or the other? At the moment
> plpgsql's scan.l seems to be the only use of '%option
> case-insensitive' but we have enough flex lexers laying about that I
> wouldn't be surprised to have this same risk elsewher
e output file is always the same. Can you show
us a diff of the generated files?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
is standard isn't just theoretical, btw. Over here, many calendars
(pocket, wall) have the week number printed on it, and people say
things like, "we will take care of that in week 37".
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Andrew M. Campbell wrote:
> I tried to build postgresql-8.0.0beta1 on an OpenBSD 3.5 (i386)
> system and it failed.
Fixed in current sources.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: Ha
create a connection
> dialogue!"
This is a pgAdmin issue, so you should report it there.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Tom Lane wrote:
> But that code is gcc-only, and he's not using gcc.
I think the icc compiler claims to be gcc-compatible in that area, so
it's quite likely that the gcc assembler code would be used.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
--
pile with SSL seems to be
> by setting appropriate CFLAGS, CXXGLAGS and LDFLAGS before running
> the configure script.
Yes, that's the standard way to go about it. No need to duplicate that
functionality.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---
age=arg) while the first is
> intended to be used to enable or disable a feature
> (--enable-feature).
This is wrong. Both variants can accept an argument or not. The
difference is only in the spelling.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
r it should be "libdir"?
Yes it should. Please change it.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
César Arnold wrote:
> Hi, I created a function called "isnull" for test
> purposes and when trying to replace it returns the
> message belows :
ISNULL is a reserved word. You need to quote the name or pick a
different one.
--
Peter Eisentraut
http://developer.pos
selected library. These libraries are
> more or less source-compatible but they do not have the same ABI, so
> mix-and-match is not going to work.
That sounds like a pretty hard problem to solve.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(e
501 - 600 of 900 matches
Mail list logo
