Bear, there is some IPv6 stuff in fe-secure.c. Is this intended? We
don't support IPv6 in the backend yet, do we. We are having portability
problems with that 'case' statement and I am considering removing it.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTE
Althought that is in the contrib/bind directory. Searching again...
Chris
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher
> Kings-Lynne
> Sent: Wednesday, 19 June 2002 2:41 PM
> To: Bruce Momjian; Hackers
> Subject: Re: [HACKERS] [COM
OK, the offending code is this:
case AF_INET6:
sin6 = (struct sockaddr_in6 *) &addr;
for (s = h->h_addr_list; *s != NULL; s++)
{
if (!memcmp(sin6->sin6_addr.s6_addr8, *s,
h->h_length))
I've just updated features.sgml to have a list of supported features
followed by a list of unsupported ones. There are some items in the
"unsupported list" which look easy to do. I've got patches for a "MATCH
SIMPLE" clause on referential integrity declarations, and am developing
patches for CREAT
I am working on the TODO item:
o Change syntax to WITH DELIMITER, (keep old syntax around?)
and I have added syntax so COPY can now accept all parameters at the end
using WITH:
COPY table
FROM { 'filename' | stdin }
[ [ WITH ]
[ BINARY
> I received this via private email. Do we want CORRESPONDING added to
> the TODO list?
Sure. Though since we now have features.sgml which has the complete set
of SQL99 itemized features we perhaps should shrink the ToDo entries
regarding SQL99 features to only one:
"Support additional SQL99 fe
Peter Eisentraut wrote:
> OK, I've been looking at this package for some time through various
> iterations and I have my doubts about it.
>
> What's going to happen to this when SHOW ALL is changed to return a query
> result? If you want to provide an example of a set-returning function,
> use
Erm... I suppose I didn't really intend to bring up domains at all.
I'm just playing trying to figure out how things work (easiest by
breaking them I think).
I don't understand why the below patch has such an adverse affect on
the system.
Causes:
(p2.pronargs != 3 OR p2.proretset OR p2.pro
Rudi,
select to_char(date_column, 'Month');
See similar under "Formatting Function" in the docs.
--
-Josh Berkus
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Tom Lane wrote:
>
> "Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
>
> > I already mentioned an opinion in 2001/09/08.
> > Both the command counters and the snapshots in a
> > function should advance except the leading SELECT
> > statements.
>
> I do not like the idea of treating the first se
> -Original Message-
> From: Dann Corbit
> Sent: Tuesday, June 18, 2002 1:51 PM
> To: Bruce Momjian; Michael Meskes
> Cc: PostgreSQL Hacker
> Subject: Re: [HACKERS] ECPG won't compile anymore
>
>
> > -Original Message-
> > From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> > Sent:
Tom Lane writes:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > I think eventually pg_ctl should be folded into the postmaster executable.
> > This would remove a great amount of possible misunderstandings between the
> > two programs.
>
> Like what?
The biggie is that pg_ctl reports the pos
I received this via private email. Do we want CORRESPONDING added to
the TODO list?
---
David H. Johnson wrote:
> Hi,
>
> I am writing you because you're listed as the TODO List maintainer. I noticed
> that PostgreSQL do
I know that Apache Group created special library to handle difference
between different platforms (including win32). They had similar problems
porting Apache to Windows. They build very portable threads api (win32,
POSIX, native Linux thread and more) There is also all IPC stuff (mutex,
signals m
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 18, 2002 11:13 AM
> To: Michael Meskes
> Cc: PostgreSQL Hacker
> Subject: Re: [HACKERS] ECPG won't compile anymore
>
>
> Michael Meskes wrote:
> > On Tue, Jun 18, 2002 at 10:29:10AM -0400, Tom Lan
Michael Meskes <[EMAIL PROTECTED]> writes:
> How about we add the preproc.c file generated by bison 1.49 to cvs?
> Could that create problems elsewhere?
Yes. It's a bad idea to put derived files in CVS. For one thing,
CVS will not guarantee that their timestamps are right compared to
the maste
Hi,
We observed a "String index out of range: 23" problem when we tried to
retrieve timestamp field value that has milliseconds. We are trying to find
a quick fix for the millisecond problem for Timestamp.
We notice there is a beta driver(devpgjdbc2.jar) that contains this fix
currently, but wa
Hi,
We have a timestamp column in one table and we are getting the above problem
when the timestamp column has a value up to milliseconds.
We are using stable PostgreSQL 7.2 jdbc driver (pgjdbc2.jar) got from
http://jdbc.postgresql.org/download.html. Does anyone know of latest
production ready d
PostgreSQL 7.2.1...
We have:
C:\CYGWIN\USR\SRC\POSTGRESQL-7.2.1-1\src\include\utils\catcache.h(84):ex
tern MemoryContext CacheMemoryContext;
C:\CYGWIN\USR\SRC\POSTGRESQL-7.2.1-1\src\include\utils\memutils.h(70):ex
tern DLLIMPORT MemoryContext CacheMemoryContext;
They cannot both be correct. Whic
Hi,
We have a timestamp column in one table and we are getting the above problem
when the timestamp column has a value upto milliseconds.
We are using PostgreSQL 7.2 version stable jdbc driver(pgjdbc2.jar) got from
http://jdbc.postgresql.org/download.html. Does anyone know of latest
production r
Michael Meskes <[EMAIL PROTECTED]> writes:
> On Tue, Jun 18, 2002 at 10:29:10AM -0400, Tom Lane wrote:
>> I'd be inclined to say that you don't commit until bison 1.49 is
>> officially released. Got any idea when that will be?
> No, that's the problem. ECPG and the backend parser are running out
"Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
>> I'm not sure exactly what you mean by "stable" here.
> Wasn't it you who defined *stable* as
> Cachable within a single command: given fixed input values, the
> result will not change if the function were to be repeatedly evaluated
> within a
Michael Meskes wrote:
> On Tue, Jun 18, 2002 at 10:29:10AM -0400, Tom Lane wrote:
> > I'd be inclined to say that you don't commit until bison 1.49 is
> > officially released. Got any idea when that will be?
>
> No, that's the problem. ECPG and the backend parser are running out of
> sync. After
How about we add the preproc.c file generated by bison 1.49 to cvs?
Could that create problems elsewhere?
The version that is part of the source tree now is generated on the
server, isn't it?
Michael
--
Michael Meskes
[EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use Post
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Peter Eisentraut wrote:
> >> _deadcode is nowadays known as CVS history.
>
> > Agreed, but _deadcode directories still exist, so I put it there.
> > Personally, I would like to see all those files removed, but I was
> > outvoted las
Hello,
I am new to PostgreSQL, but I am interested in the Win32 port.
I have studied the architecture of other databases like Oracle.
They have had to turn their multi-process model used on Unix into a fully
multi-threaded one on Win32. I have the feeling that they have had the same
debate that
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
>
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Sorry, I don't understand ...
>
> > Let t be a table which is defined as
> > create table t (id serial primary key, dt text);
> > Then is the following
Chris, Tom:
Yes, thank you Chris, I meant a builtin SQL function.
> > Given the amount of qoute nesting we do in Postgres, I thought that
> we need a
> > function that handles automatic doubling of quotes within strings.
> I've
> > written one in PL/pgSQL (below). I'd really love to see thi
On Tue, Jun 18, 2002 at 03:24:57PM +0200, Michael Meskes wrote:
> On Mon, Jun 17, 2002 at 11:27:45AM -0700, Dann Corbit wrote:
> > Here is the complete NIST regression test:
> > ftp://cap.connx.com/pub/chess-engines/new-approach/nist.ZIP
> >
> > You have to use passive ftp to get files from my si
Gotcha. 'twas the first time I encountered it, I wasn't expecting it.
Thank you for the clarification. I hadn't paid attention to that
paragraph when I read over it.
David
Tom Lane wrote:
>David Ford <[EMAIL PROTECTED]> writes:
>
>
>>heakin=> \z
>>Access privileges for database "heakin"
>
On Tue, 2002-06-18 at 09:07, Jan Wieck wrote:
> Dann Corbit wrote:
> >
> > The startup stuff for PostgreSQL is just a few files. It does not seem
> > insurmountable to change it. But it is none of my business. If it is a
> > major hassle (for reasons which I am not aware) then I see no driving
On Tue, Jun 18, 2002 at 10:29:10AM -0400, Tom Lane wrote:
> I'd be inclined to say that you don't commit until bison 1.49 is
> officially released. Got any idea when that will be?
No, that's the problem. ECPG and the backend parser are running out of
sync. After all bison's release may be later
"Rod Taylor" <[EMAIL PROTECTED]> writes:
> This appears to be due to makeTypeCast() in gram.y which bypasses
> creating a TypeCast node for simple A_Const.
My immediate reaction is that you've probably put the testing of
domain constraints in the wrong place. You didn't say exactly
what your imp
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I think eventually pg_ctl should be folded into the postmaster executable.
> This would remove a great amount of possible misunderstandings between the
> two programs.
Like what?
The thing pg_ctl needs to know is where PGDATA is, and that
unfortunat
David Ford <[EMAIL PROTECTED]> writes:
> heakin=> \z
> Access privileges for database "heakin"
>Table | Access privileges
> ---+---
> interviewers |
> heakin=> grant select,insert,update on interviewers to heakin;
> GRANT
> heakin=> \z
> Access
[EMAIL PROTECTED] writes:
> What if BasicOpenFile() got some other error?
Doesn't really matter; anything else would be a problem we can't recover
from anyhow. Besides, given that rename is failing with ENOENT, a
conflict on the destination name does not appear to be the issue.
Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Sorry, I don't understand ...
> Let t be a table which is defined as
> create table t (id serial primary key, dt text);
> Then is the following function *stable* ?
> create function f1(int4) returns text as
> '
> declare
> t
Josh Berkus <[EMAIL PROTECTED]> writes:
> Given the amount of qoute nesting we do in Postgres, I thought that we need a
> function that handles automatic doubling of quotes within strings. I've
> written one in PL/pgSQL (below). I'd really love to see this turned into a
> builtin C function.
Jan Wieck <[EMAIL PROTECTED]> writes:
> Perform has nothing to do with ORACLE. It was added because people tried
> to call other "procedures" and didn't want any result back.
Well, in that case we can do what we want with it.
Does anyone object to making it set FOUND?
re
Michael Meskes <[EMAIL PROTECTED]> writes:
> I finally hit bison's limit and cannot find any easy to remove rules in
> the ecpg part of the parser anymore. There may be some in the backend
> part, but I'd like to keep those in sync.
> So what do we do?
I'd be inclined to say that you don't commi
Dann Corbit wrote:
>
> > -Original Message-
> > From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, June 17, 2002 6:20 PM
> > To: Dann Corbit
> > Cc: Jan Wieck; Peter Eisentraut; PostgreSQL-development
> > Subject: Re: [HACKERS] Roadmap for a Win32 port
> >
> >
> > Dann Corbi
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Peter Eisentraut wrote:
>> _deadcode is nowadays known as CVS history.
> Agreed, but _deadcode directories still exist, so I put it there.
> Personally, I would like to see all those files removed, but I was
> outvoted last time I asked.
Perhaps we ne
On Mon, Jun 17, 2002 at 11:27:45AM -0700, Dann Corbit wrote:
> Here is the complete NIST regression test:
> ftp://cap.connx.com/pub/chess-engines/new-approach/nist.ZIP
>
> You have to use passive ftp to get files from my site because of the
> firewall.
I'm pretty sure my proxy does use passive f
I finally hit bison's limit and cannot find any easy to remove rules in
the ecpg part of the parser anymore. There may be some in the backend
part, but I'd like to keep those in sync.
For the time being I update my machine to a development snapshot bison
1.49, but that doesn't look like a good so
Tom Lane wrote:
>
> James Thornton <[EMAIL PROTECTED]> writes:
> > I am not running NFS on this system.
>
> Oh well, scratch that theory. Perhaps you should tell us what you *are*
> running --- what OS, what hardware? I still believe that this must be
> a system-level bug and not directly Post
Tom Lane wrote:
>
> That really should be impossible --- it says that a rename() failed for
> a file we just created.
>
> I judge from the spelling of the error message that you are running 7.1.
7.1.3
> However, given that you state a system reboot is necessary and
> sufficient to make the prob
46 matches
Mail list logo
