Hi David
I seem to recall the last time that I built Postgres on windows using
VC++, there was a whole load of compiler warnings, because MS have
taken it upon themselves to deprecate various C std lib functions (in
particular, string.h functions). You're supposed to use their
non-standard
Hi,
I'm researching if smallint can be made a higher-class citizen of our type
system than currently.
Does anyone know where to find the discussion refered to here?
http://archives.postgresql.org/pgsql-hackers/2008-10/msg01485.php
I did some searches on the archives but no keywords I search for
Tom Lane t...@sss.pgh.pa.us wrote:
+1 for adding parens; we might want to make a function of it
someday.
How about IsolationUsesXactSnapshot
Patch attached.
Joe said that he'll review this weekend and probably commit in a day
or two if there are no objections.
-Kevin
***
I wrote:
Alexey Klyukin al...@commandprompt.com writes:
I always wondered why ps ax|grep postgres shows several extra blank lines
after the process name, i.e.
AFAIR it's always done that on OSX. I thought we'd tried the '\0'
padding way back when and it didn't work nicely, but maybe Apple
Alvaro Herrera alvhe...@alvh.no-ip.org writes:
I'm researching if smallint can be made a higher-class citizen of our type
system than currently.
Does anyone know where to find the discussion refered to here?
http://archives.postgresql.org/pgsql-hackers/2008-10/msg01485.php
I think this was
Tatsuo Ishii is...@postgresql.org writes:
Is there any way to use regclass without having ERROR?
pgpool-II needs to find the oid from table name and for the purpose it
issues something like SELECT 'table_name'::regproc::oid. Problem is,
if the table does not exist, an error occured and
On Fri, Sep 3, 2010 at 7:09 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I wrote:
Alexey Klyukin al...@commandprompt.com writes:
I always wondered why ps ax|grep postgres shows several extra blank lines
after the process name, i.e.
AFAIR it's always done that on OSX. I thought we'd tried the '\0'
On Fri, Sep 3, 2010 at 5:53 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Sep 3, 2010 at 2:04 PM, Tom Lane t...@sss.pgh.pa.us wrote:
On reflection I think that for parameterized paths the problem won't be
too bad, because (a) we'll ignore
On Fri, Sep 3, 2010 at 6:24 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Now the HS case likewise appears to be set up so that the signal can
only directly interrupt ProcWaitForSignal, so I think the core issue is
whether any deadlock situations are possible. Given that this gets
called from a
Excerpts from Tom Lane's message of vie sep 03 19:36:06 -0400 2010:
Does anyone know where to find the discussion refered to here?
http://archives.postgresql.org/pgsql-hackers/2008-10/msg01485.php
I think this was the last time I tried it:
On Fri, Sep 3, 2010 at 9:19 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
The problem I'm facing is functions declared to take type smallint not
working unless the integer literal has an explicit cast. Currently the
best answer is simply to avoid using smallint in functions, but this
Robert Haas robertmh...@gmail.com writes:
Maybe the lexer isn't the right place to fix this. The problem here
(or so I gather) is that if I say foo(1), then 1 is an integer and
we'll do an implicit cast to bigint, real, double precision,
numeric, oid, or reg*, but the cast to smallint is
Alvaro Herrera alvhe...@commandprompt.com writes:
Excerpts from Tom Lane's message of vie sep 03 19:36:06 -0400 2010:
On the whole I'm still afraid that changing the initial typing of
integer constants is going to break a lot of code while buying not much.
Do you have a specific reason for
Hello
I am looking on ToDo topic - Allow handling of %TYPE arrays, e.g.
tab.col%TYPE[]
Some the most simple solution can be enhancing regtype to support this
syntax - this can be relative simple, and it can be useful for other
PL and for dynamic SQL too. It can be simple test - if some table has
101 - 114 of 114 matches
Mail list logo
