Just an FYI regarding this bug:
http://archives.postgresql.org/pgsql-bugs/2009-12/msg00267.php
Windows always uses UNICODE to store file and directory names.
The wide-char version of any WIN32 API call will accept or return data in
UTF-16 encoded Unicode, regardless of the local environment's s
A curiosity question regarding torn pages: How does this work on file systems
that don't write in-place, but instead always do copy-on-write?
My example would be Sun's ZFS file system (In Solaris & BSD). Because of its
"snapshot & rollback" functionality, it never writes a page in-place, but
> -Original Message-
> From: Andrew Dunstan [mailto:and...@dunslane.net]
> Sent: Tuesday, November 17, 2009 9:15 AM
> To: Peter Eisentraut
> Cc: Chuck McDevitt; Itagaki Takahiro; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] UTF8 with BOM support in psql
>
>
> -Original Message-
> From: Peter Eisentraut [mailto:pete...@gmx.net]
> Sent: Tuesday, November 17, 2009 9:05 AM
> To: Chuck McDevitt
> Cc: Itagaki Takahiro; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] UTF8 with BOM support in psql
>
> On tis, 2009-11-
>
> I don't know what the best solution is here. The BOM encoded as UTF-8
> is valid data in other encodings. Of course, there is your point that
> such data cannot be at the start of an SQL command.
>
Is the UTF-8 BOM ( EF BB BF ) actually valid data in any other multi-byte
encoding (other t
be ported (m4 is already ported).
I'm also wonderings why flex is a problem, since there is a GNUwin32 (native)
port of Bison 2.4.1 and m4,
And Bison uses m4 these days, doesn't it? Perhaps it wouldn't be so hard to
update flex to use the same m4 calling that bison uses?
Chuck McDevitt
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
> -Original Message-
> From: pgsql-hackers-ow...@postgresql.org [mailto:pgsql-hackers-
> ow...@postgresql.org] On Behalf Of Stephen Frost
> Sent: Tuesday, June 16, 2009 5:47 AM
> To: Greg Stark
> Cc: Robert Haas; Jeremy Kerr; ; Alvaro
> Herrera; Stefan Kaltenbrunner; Gurjeet Singh
> Subject
> -Original Message-
> From: pgsql-hackers-ow...@postgresql.org [mailto:pgsql-hackers-
> ow...@postgresql.org] On Behalf Of Simon Riggs
> Sent: Tuesday, May 19, 2009 4:32 AM
> To: pgsql-hackers
> Subject: [HACKERS] Multiple sorts in a query
>
>
> Just wanted to check some thoughts about
Why are certain character encodings not legal for the server_encoding?
For example, we allow EUC_KR, but disallow UHC, which is a superset of EUC_KR.
What are the rules for what is or is not allowed as server_encoding?
Is it having a conversion to MIC that is the issue? Why is that important fo
Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Tuesday, March 17, 2009 11:26 AM
> To: Chuck McDevitt
> Cc: Zdenek Kotala; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Solaris getopt_long and PostgreSQL
>
> Chuck McDevitt writes:
> &g
etopt_long. For those, you get "-p" is not a valid user.
This is because MAC, BSD and GNU getopt_long permutes the arguments, and our
getopt_long does not.
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: Tuesday, March 17, 2009 11:02 AM
&g
About a year ago, you talked to the PostgreSQL people about some problem with
Solaris getopt_long, and they changed the build to use the internal getopt_long
instead of the Solaris one?
What was the problem with Solaris getopt_long? Does the problem still exist in
Solaris 10?
My users are unh
What if the block of text is split in the middle of a multibyte character?
I don't think it is safe to assume raw blocks always end on a character
boundary.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailp
Doesn't ANSI standard interval syntax have the minus sign before the quotes?
Select interval -'2008-10';
???
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
> [EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: Saturday, November 08, 2008 11:39 AM
> To: Ron Mayer
> Cc:
There is a problem trying to make Postgres do these things in Parallel.
The backend code isn't thread-safe, so doing a multi-thread
implementation requires quite a bit of work.
Using multiple processes has its own problems: The whole way locking
works equates one process with one transact
If you are talking about working on the code (internals), I find eclipse
works very well for working on PostgreSQL.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pedro Belmino
Sent: Monday, October 01, 2007 6:42 AM
To: pgsql-hackers@postgresql.org
Subject: [HACKERS] IDE
Hel
> >
> > Many of us would like to see libedit ported to Windows too ;-)
>
> Yeah, it's on my (insanely long) TODO to look at sometime :-)
>
> //Magnus
I've thought about working on a libedit port myself, but I don't see how
that would help PostgreSQL unless the PostgreSQL community would be
willi
y.def
(note: dlltool won't overwrite a def file if it exists).
But why would this be necessary? It looks like the readline
distribution is broken.
> -Original Message-
> From: Chuck McDevitt
> Sent: Monday, September 24, 2007 11:59 PM
> To: 'Magnus Hag
ib commands, allowed me to link with no
errors or warnings.
Maybe I need to do some research on readline... this seems more
complicated than I expected.
Does no one else use readline on Windows? Is the Gnuwin32 readline a
fraud? I just don't know.
> -Original Message-
&
-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 24, 2007 1:30 AM
> To: Chuck McDevitt
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Suggestion for MSVC build
>
> What version readline are you using?
>
> I tried with the latest
Also, I think I told you the wrong file to link to. I think it is the
.a files, not the .lib files.
Let me check on that.
> -Original Message-
> From: Chuck McDevitt
> Sent: Monday, September 24, 2007 10:34 AM
> To: 'Magnus Hagander'
> Cc: pgsql-hackers@pos
rom: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 24, 2007 1:30 AM
> To: Chuck McDevitt
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Suggestion for MSVC build
>
> What version readline are you using?
>
> I tried with the latest download
, you could have the perl code issue "attrib"
commands on the target location for each file it is moving. Better if
there is some more "perl" way to do this.
> -Original Message-
> From: Magnus Hagander [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 24, 200
r any files set read-only.
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: Sunday, September 23, 2007 7:45 PM
> To: Chuck McDevitt
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Problem with MSVC install script
>
>
>
&
It seems like there isn't any good reason the perl scripts for the MSVC
build don't support readline
Readline for windows is available as part of the GnuWin32 project.
http://gnuwin32.sourceforge.net/packages/readline.htm
It normally installs to "c:\Program Files\GnuWin32"
I'd upda
I was trying out the msvc support, and ran into a minor problem in the
install.bat/install.pl
If any files that are going to be installed are marked read-only, they
carry the read-only attribute with them when they get copied to the
install dir.
Then, if you try to run install again, the ne
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
> [EMAIL PROTECTED] On Behalf Of Florian G. Pflug
> Sent: Thursday, August 23, 2007 11:04 AM
> To: Ben Tilly
> Cc: Michael Glaesemann; Gregory Stark; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] SQL feature req
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 23, 2007 10:26 AM
> To: Chuck McDevitt
> Cc: Tom Lane; Gregory Stark; Michael Glaesemann; Ben Tilly; pgsql-
> [EMAIL PROTECTED]
> Subject: Re: [HACKERS] SQL feature requ
>
> > This seems like a particularly petty case compared to a lot of other
> > extensions we do allow.
>
> That's exactly the problem. Most of our other extensions are
justified
> by some significant capability gain. This isn't --- it provides zero
> new functionality, and the "convenience" fac
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
> [EMAIL PROTECTED] On Behalf Of Chuck McDevitt
> Sent: Wednesday, August 22, 2007 11:53 PM
> To: Michael Glaesemann; Ben Tilly
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS]
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
> [EMAIL PROTECTED] On Behalf Of Michael Glaesemann
> Sent: Wednesday, August 22, 2007 5:17 PM
> To: Ben Tilly
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] SQL feature requests
>
>
> On Aug 22, 2007, at 1
Is protocol version 2 still used by anything? Is there a reason why
this is still supported?
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
stems
where 'xxx' is either a varchar or char type, in all contexts, and
implicit casts handle any needed conversions.
But now I understand why it does things this way.
Thanks.
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 12, 2007 9:50 PM
To
Just a curiosity question: Why is the type of a literal '1' "unknown"
instead of varchar(1)?
Wouldn't varchar(1) cast properly to any use of the literal '1'?
What is the benefit of assuming it's an unknown?
---(end of broadcast)---
TIP 7: You ca
s fixing this on the TODO list?
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 10, 2007 5:11 PM
To: Gregory Stark
Cc: Chuck McDevitt; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Why is this allowed?
Gregory Stark <[EMAIL PROTECTED]> wri
Why don't we have some kind of error check for people entering things
like INTERVAL '1' DAY in their query, since we don't handle it.
select now() =now() + interval '1' day;
?column?
--
T
This seems scary... We allow something through and then ignore it?
"Interval '1 day'
title like "sum(WeeklySales)"
-Original Message-----
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 31, 2006 10:38 PM
To: Chuck McDevitt
Cc: Stephan Szabo; beau hargis; pgsql-sql@postgresql.org;
pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] [SQL] Case Preservati
-Original Message-
From: Stephan Szabo [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 31, 2006 10:23 AM
To: Chuck McDevitt
Cc: Tom Lane; beau hargis; pgsql-sql@postgresql.org;
pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] [SQL] Case Preservation disregarding case
On Tue, 31 Oct
r 30, 2006 10:35 PM
To: Chuck McDevitt
Cc: beau hargis; pgsql-sql@postgresql.org; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] [SQL] Case Preservation disregarding case
sensitivity?
"Chuck McDevitt" <[EMAIL PROTECTED]> writes:
> At Teradata, we certainly interpreted the
as
entered by the user.
So, your example would work just fine.
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Monday, October 30, 2006 10:35 PM
To: Chuck McDevitt
Cc: beau hargis; pgsql-sql@postgresql.org; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] [SQL] Case
At Teradata, we certainly interpreted the spec to allow case-preserving,
but case-insensitive, identifiers.
Users really liked it that way: If you re-created a CREATE TABLE
statement from the catalog, you could get back exactly the case the user
had entered, but people using the table didn't need
-Original Message-
I think we had that problem solved too in principle: build the new
catalogs in a new $PGDATA directory alongside the old one, and hard-link
the old user table files into that directory as you go. Then pg_upgrade
never needs to change the old directory tree at all. This
From my experience with Visual C++, using /Za isn't a good idea.
When you set that, the compiler become very pedantic about following the
ANSI speck to the letter, which usually means common posix functions
aren't available under their normal names (The ansi spec says if the
compiler defines functi
x27;t tie us to an ancient compiler
(Well, it came out in the end of 1998, and I consider it ancient).
> -Original Message-
> From: Dave Page [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 05, 2006 3:12 PM
> To: Chuck McDevitt; [EMAIL PROTECTED]; [EMAIL PROTECTED];
pgsql-
it automatically calls them for .y and .l files.
-Original Message-
From: Magnus Hagander [mailto:[EMAIL PROTECTED]
Sent: Friday, May 05, 2006 12:42 AM
To: Gurjeet Singh; pgsql-hackers@postgresql.org; [EMAIL PROTECTED];
Chuck McDevitt
Subject: RE: [pgsql-hackers-win32] [HACKERS] Bu
Another vote for libedit support... We at Greenplum definitely want to
use it.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Pgindent adds spaces after the stars if it doesn't recognize the thing
before the star as a typedef... Could it be that somehow the list of
typedefs included in pgindent got corrupted?
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
> [EMAIL PROTECTED] On Behalf Of To
Just for fun, I went through PostgreSQL 8.1 and did a
complete build using Microsoft’s C and the latest Visual Studio.
With a few minor tweaks, everything compiled with no errors.
My assumption is that because PostgreSQL is a
UNIX/Linux-centric project (and gcc/gdb centric), this reall
names don't get
mangled. Only actual calls to the Win32 API would likely be __stdcall.
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 19, 2005 5:22 AM
> To: Tom Lane
> Cc: Chuck McDevitt; PostgreSQL-development
> Subject
I think it's because it's __stdcall, and the name gets mangled to
include the number of parameters.
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 18, 2005 4:44 PM
> To: Chuck McDevitt
> Cc: Tom Lane; PostgreSQL-
IPv6 exists in a "production quality" state only in XP sp1, XP sp2, and
Windows 2003.
There was an optional prototype stack for 2000, but not production
quality and not installed by default. XP non-service-pack had IPv6,
but not production-quality.
One thing you could do is dynamically load get
The definition in WS2tcpip.h
WINSOCK_API_LINKAGE
int
WSAAPI
getaddrinfo(
IN const char FAR * nodename,
IN const char FAR * servname,
IN const struct addrinfo FAR * hints,
OUT struct addrinfo FAR * FAR * res
);
(IN, FAR, and OUT are #defined to empty string).
WINSOCK_API_LINK
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
> [EMAIL PROTECTED] On Behalf Of Dave Held
> Sent: Tuesday, May 03, 2005 3:41 PM
> To: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Feature freeze date for 8.1
>
> > -Original Message-
> > From: Tom La
> -Original Message-
> From: Oliver Jowett [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 02, 2005 3:06 PM
> To: Chuck McDevitt
> Cc: Tom Lane; [EMAIL PROTECTED]; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Feature freeze date for 8.1
>
> Chuck McDevi
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
> [EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: Monday, May 02, 2005 1:17 PM
> To: [EMAIL PROTECTED]
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Feature freeze date for 8.1
>
> Andrew - Supernews <[EM
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-hackers-
> [EMAIL PROTECTED] On Behalf Of Dave Held
> Sent: Friday, April 22, 2005 10:23 AM
> To: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Woo hoo ... a whole new set of compiler
> headaches!! :)
>
> > -Origina
Can you tell me more about the good ODBC driver being worked on?
I was thinking of working on this myself, but if someone is already
solving the problem, that's great!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Joshua D. Drake
Sent: Sunday, April 17,
57 matches
Mail list logo
