On Sat, Oct 25, 2008 at 12:36:24PM -0400, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > If the write is interrupted by a timeout or cancel, can anything
> > be done here or elsewhere to abort the statement and release its
> > locks?
>
> The best
to
execute a query that returns enough data to fill both the client's
and the server's socket buffers, then go to sleep without reading
the response).
--
Michael Fuhr
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ther users.
Are any prepared transactions still open?
select * from pg_prepared_xacts;
--
Michael Fuhr
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
http://www.securityfocus.com/archive/1/471541/30/0/threaded
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
um, so I assume it doesn't.
Doesn't appear to, at least not using the test case I found for 8.1
and later.
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an
improved
immediately.
INFO: "pg_shdepend": found 8475403 removable, 3907 nonremovable row versions
in 76783 pages
--
Michael Fuhr
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
ecome zero, which should be within 15 seconds. Repeating the
experiment should reveal a 15-second cycle of statistics resets.
In case this behavior is platform-dependent I'm testing on Solaris 9
sparc.
--
Michael Fuhr
---(end of broadcast)---
T
0 | 0
pg_toast_1260|0 |0 | 0 | 0 | 0
pg_toast_1262|0 |0 | 0 | 0 | 0
pg_toast_2396|0 |0 | 0 | 0 | 0
(10 rows)
--
Michael Fuhr
---
9). PostgreSQL doesn't currently support such conversions
but it's something to be aware of.
--
Michael Fuhr
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
3, not 6? Or does that 2-byte
SHIFT_JIS_2004 sequence have a 1-byte sequence in another supported
encoding? Or am I missing something?
--
Michael Fuhr
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
urrently using
MRTG to execute Perl scripts that query the statistics views and
I've been thinking about rewriting those scripts to be AgentX
subagents so they'd be queryable via SNMP.
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versi
On Tue, Mar 27, 2007 at 07:33:08AM -0400, Andrew Dunstan wrote:
> We can certainly provide a different view, or sort it by system name,
What about making the column headers clickable to control the sort
order?
--
Michael Fuhr
---(end of broadc
nto the database, and this release properly accepts
only valid UTF-8 sequences. One way to correct a dumpfile is to run
the command iconv -c -f UTF-8 -t UTF-8 -o cleanfile.sql dumpfile.sql."
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Sat, Mar 10, 2007 at 05:39:37PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > I'll submit a patch -- any preferences for silent continuation vs.
> > continuation with a notice or warning?
>
> I think silent is fine for ENOENT cases. We k
On Sat, Mar 10, 2007 at 12:32:04PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > I'm wondering if the code should check for ENOENT if stat() fails
> > and either skip this entry silently under the assumption that the
> > file had been d
errmsg("could not stat file \"%s\": %m", filename)));
dirsize += fst.st_size;
}
I'm wondering if the code should check for ENOENT if stat() fails
and either skip this entry silently under the assumption that the
file had been deleted since the call to ReadDir(), or
port USING
DELIMITERS. COPY tablename does, so it has worked all along.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
SING DELIMITERS kept for backward compatibility. 2002-06-15 */
opt_using DELIMITERS Sconst
What should be fixed -- COPY or \copy? Does psql's \copy still
need backward compatibility to unsupported pre-7.3?
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
stumble across it in a test environment.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
minor differences in the rendered
glyphs, which tells me that I am indeed receiving the decomposed
sequences.
Thanks!
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail com
x
+--
(0,1) |1
(4,92) | 1000
(2 rows)
test=> VACUUM foo;
VACUUM
test=> SELECT ctid, x FROM foo;
ctid | x
+--
(0,1) |1
(4,92) | 1000
(2 rows)
test=> VACUUM FULL foo;
VACUUM
test=> SELECT ctid, x FROM foo;
ctid | x
inserts.
>
> Can this code is useful for postgresql community?
Are you familiar with the contrib/ian module that will be in 8.2?
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
people who ask for the feature would find
this a satisfactory answer :-("
http://archives.postgresql.org/pgsql-hackers/2005-11/msg00579.php
http://archives.postgresql.org/pgsql-hackers/2005-11/msg00580.php
--
Michael Fuhr
---(end of broadcast)--
out releasing 8.1.5 soon I'm
hoping to submit a patch before that happens.
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On Tue, Sep 12, 2006 at 02:31:22PM -0400, Bruce Momjian wrote:
> I again will not be able to complete the release notes today as
> promised. My next target date is Monday, August 18. Sorry.
The next Monday, August 18, is in 2008. Surely that'll be
enough time ;-)
--
M
On Sun, Sep 10, 2006 at 07:38:24PM -0400, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > I spent a few minutes doing the same tests I did a few months ago
> > and found problems with dblink and ltree; I'll submit patches for
> > those. Tom, do y
contrib/xml2 currently has PG_MODULE_MAGIC in xslt_proc.c, which
results in a runtime error on systems that built the module without
support for libxslt per the comments in the Makefile. Should
PG_MODULE_MAGIC be in xpath.c instead?
--
Michael Fuhr
---(end of broadcast
, do you recall which modules gave you trouble?
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
dule, as shown by getting errors if you then try to reinstall it).
> >Seems like this area needs more attention ... anyone want to work on it?
>
> I'll take it. How long do I have?
For reference, here are some comments about the cleanup work I did
a while back:
http:
ant people to register
to read the specification; you can get there from here:
http://www.opengroup.org/online-pubs-short?DOC=9699959299&FORM=HTML
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
names are passed as written, so I'm not seeing how the
case-insensitivity rules are being applied. Should this be reworded
or omitted altogether? Or is there something I'm missing?
Other comments? Thanks.
--
Michael Fuhr
---(end of broadcast)-
her
PyObject_Str() can possibly return NULL, but several occurrences
of the above code snippet caught my eye because we had dealt with
it before.
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire
anywhere.
>
> Damifino ... Jan might remember.
Retrieve-Instead-Retrieve, according to this message from Jan:
http://archives.postgresql.org/pgsql-hackers/2003-03/msg01219.php
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
ext=PGC_POSTMASTER) at guc-file.l:152
#3 0x0025d80c in SelectConfigFiles (userDoption=0x1 , progname=0x390610 "postgres") at guc.c:2867
#4 0x0019a450 in PostmasterMain (argc=5, argv=0x391240) at postmaster.c:602
#5 0x001518c8 in main (argc=5, argv=0x391240) at main.c:187
--
Michael
In README.pgcrypto, Section 2.3 "Deprecated functions" says that
digest_exists(), hmac_exists(), and cipher_exists() are planned to
be removed in PostgreSQL 8.2. Those functions still exist -- should
they be removed or does that section need updating?
--
Mi
On Thu, Aug 03, 2006 at 12:05:23PM -0400, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > Set tg_trigtuple/tg_newtuple in AFTER triggers according to whether
> > old and new tuples were supplied rather than blindly setting them
> > according to the eve
pg_dump in HEAD is dumping the entire contents of system catalogs.
New feature? :-(
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED
On Mon, Jul 31, 2006 at 11:12:14AM -0400, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > I've noticed that tg_trigtuple and tg_newtuple aren't cleared to
> > NULL in AFTER STATEMENT triggers. Is that an oversight,
>
> Probably. S
me other reason?
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
l. Prefixing each command with pgXX is a minor nuisance
but by being explicit I always know what version I'm using.
What are others doing?
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
.postgresql.org/pgsql-hackers/2006-02/msg00165.php
>
> But i don't understand why that thread is related to the TODO item,
> i'm missing something?
Possibly the message renumbering that Tom griped about:
http://archives.postgresql.org/pgsql-www/2006-07/msg00061.php
--
Michael
? If not, are there good reasons for doing it
one way or the other? I haven't considered the implications
thoroughly enough to have a position either way.
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usen
od(), both declared in
utils/builtins.h and defined in src/backend/utils/adt/format_type.c.
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Sun, Jun 18, 2006 at 07:18:07PM -0600, Michael Fuhr wrote:
> Maybe I'm misreading the packet, but I think the query is for
> ''kaltenbrunner.cc (two single quotes followed by kaltenbrunner.cc)
Correction: ''.kaltenbrunner.cc
--
Michael Fuhr
-
unner.cc" and
> failing.
Maybe I'm misreading the packet, but I think the query is for
''kaltenbrunner.cc (two single quotes followed by kaltenbrunner.cc)
and the DNS server is responding with SRVFAIL.
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
anoncvs (svr4, 66.98.251.159) is still slow responding to "cvs update";
it's been spotty for about a week now. Tcpdump shows connections being
established but then long delays for ACKs, sometimes long enough for cvs
to time out. Any updates on what's going o
stgresql.org (66.98.251.159) has been slow for a couple
of days -- it just took over five minutes to do a cvs update of
HEAD where it usually takes thirty seconds or less.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you
On Fri, May 12, 2006 at 06:39:44PM -0400, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > If $PGDATA/dh1024.pem exists and if SSL connections are enabled,
> > then each SSL connection logs the following:
> > DH_check error (dh1024.pem): No SSL error re
the hardcoded parameters. The SSL connection
works, but with DH parameters other than intended.
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command
t; a pretty narrow scenario.
Thanks -- I was just wondering if the behavior was expected or not.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
6.03 rows=2 width=4)
Index Cond: ((id = 1) OR (id = 2))
(2 rows)
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
|2 | bar-2
5 | 3 | foo-3 |1 | bar-1
6 |3 | foo-3 |2 | bar-2
(6 rows)
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
isplay a stack trace. To see examples
search the archives for words like "gdb" and "stack trace"
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
xt)))->type) == T_AllocSetContext", File:
"mcxt.c", Line: 612)
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
quot;
would be a "limited cascade" whereby DROP TYPE would cascade to the
I/O functions but would raise an error if other dependent objects
still exist.
Comments? Other possibilities?
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versi
On Sun, Mar 05, 2006 at 09:54:02PM +0800, Christopher Kings-Lynne wrote:
> contrib/vacuumlo perhaps?
vacuumlo only calls lo_unlink(); the data still exists in pg_largeobject
due to MVCC.
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have
the space for re-use by PostgreSQL without shrinking
the file (unless the table has no live tuples, in which case the
file size will be zeroed).
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
ed commands acquire ACCESS EXCLUSIVE,
just that certain commands do. TRUNCATE isn't shown.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
ire registration to read.
If that's true then it seems silly that they're available to anybody
who knows the URL.)
> Can we assume 'id' is on all unix systems?
It's defined in Shell and Utilities (XCU). If the system doesn't
have it then one must wonder what else t
On Thu, Mar 02, 2006 at 02:49:13PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > Would it make sense for DROP TYPE to have some kind of limited
> > cascade so you could drop a type and its I/O functions at the same
> > time, but still get an error
On Thu, Mar 02, 2006 at 12:52:05AM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > ... I started to work on a patch but I wasn't sure how
> > to handle the chicken-and-egg situation of dropping a type and its
> > I/O functions. Is there an
l.conf.
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
have no gaps.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
were
never created. I started to work on a patch but I wasn't sure how
to handle the chicken-and-egg situation of dropping a type and its
I/O functions. Is there any way to do that other than DROP TYPE
CASCADE? Should the uninstall scripts be doing that?
--
Mi
t;
This breaks several things, including pg_dump. A newly-initdb'd
cluster doesn't have the problem. Was something changed that should
have bumped the catalog version?
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In version
see the effect).
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
this behavior (e.g, psql, Pgadmin etc).
Are you cutting and pasting from one window into another? If so
then I wonder if something like the terminal's buffer size is the
problem.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
vice.conf? Hardly anybody ever mentions it
even though the libpq documentation refers to it; I wonder how many
people even know it exists.
http://www.postgresql.org/docs/8.1/interactive/libpq.html#LIBPQ-CONNECT
http://www.postgresql.org/docs/8.1/interactive/libpq-envars.html
--
Mic
) Did plenty of that, though usually on 3C00-3FFF.
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
On Fri, Feb 17, 2006 at 09:35:32PM -0400, Marc G. Fournier wrote:
> Sorry, I was still in Junior High in '82 :( Man, you are *old* :)
Anybody know some reasonable postgresql.conf settings for a system
that starts up with
Cass?
Memory Size?
'cuz I still have one :-)
--
ems, PgFoundry ingots? :)
Tusks? (Extensions of the elephant.)
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
messa
ecstatic, bitter, and conflicted.
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
include creating unanalyzed tables in dire need of vacuuming.
2. Use createdb or CREATE DATABASE to create a new database using
the database in (1) as the template.
3. Run tests in the new database.
4. Repeat (2) and (3) as necessary.
--
Michael Fuhr
---(end of broa
familiar with reading the pg_stats view.
http://www.postgresql.org/docs/8.1/interactive/catalog-pg-statistic.html
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan
t this un-vacuum to have? What problem are
you trying to solve?
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
quence functions like nextval()
to take a regclass argument (the sequence OID) instead of a text
argument (the sequence name); that would affect what gets put in
the function's cached plan.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have y
On Tue, Jan 10, 2006 at 07:44:23PM -0700, Michael Fuhr wrote:
> I just ran "cvs update" in my 8.1 source tree and it took nearly
> 25 minutes to complete; it usually takes about 30-60 seconds. Is
> anybody else seeing problems?
I forgot to mention that th
I just ran "cvs update" in my 8.1 source tree and it took nearly
25 minutes to complete; it usually takes about 30-60 seconds. Is
anybody else seeing problems?
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, t
On Fri, Dec 30, 2005 at 11:02:20AM -0700, Michael Fuhr wrote:
> On Fri, Dec 30, 2005 at 03:15:03AM -0500, Sebastian wrote:
> > Any ideas for a temporary work around?
>
> You could try querying the system catalogs directly instead of using
> the information_schema views;
It's been several hours since Tom's "Repair EXPLAIN failure" commit
but anonymous CVS doesn't have it yet. That seems slower than usual;
are there any problems?
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posti
t; to see what kinds of queries to
make. See also "System Information Functions" and "System Catalogs"
in the documentation.
http://www.postgresql.org/docs/8.1/interactive/functions-info.html
http://www.postgresql.org/docs/8.1/interactive/catalogs.html
--
Michael Fuhr
-
columns; with more columns the time continues to
increase although not as sharply. I don't see such an increase in
8.0.5. Querying the views individually doesn't take long; I wonder
if the planner is doing something wrong with the join operation.
--
Michael Fuhr
-
gt; EXPLAIN SELECT * FROM information_schema.element_types;
ERROR: record type has not been registered
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
e client's stdin and stdout. The client
writes data to and reads data from the connection using the API
functions for doing so; where the client gets or puts that data is
up to the application.
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
plode("\t", rtrim($row)));
}
fclose($fh);
According to the PHP documentation fputcsv() is new as of 5.1.0RC1;
for earlier versions you could probably find a module to generate
CSV output.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
is too big" error if you have more than about 405 columns.
With short, non-TOASTed data you'll be able to insert more columns.
--
Michael Fuhr
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
Does contrary behavior from MySQL count as evidence that PostgreSQL's
behavior is correct? :-)
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
--+
| EXTRACT(MICROSECOND FROM '2003-01-02 10:30:00.00123') |
+---+
| 1230 |
+---+
1 row in set (0.01 sec)
--
Michael Fuhr
---(end of bro
x27;2003-01-02 10:30:00.00123');
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use
near 'FROM '2003-01-02 10:30:00.00123')' at line 1
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ted one just a couple of days ago:
http://archives.postgresql.org/pgsql-general/2005-12/msg00191.php
> (I'll credit you in the MySQL Compat Library code btw) If you're
> interested, you'd be welcome to join the project btw...
I haven't been follo
On Tue, Dec 06, 2005 at 01:05:12AM -0700, Michael Fuhr wrote:
> CREATE FUNCTION inet2num(inet) RETURNS numeric AS $$
> DECLARE
> a text[] := string_to_array(host($1), '.');
> BEGIN
> RETURN a[1]::numeric * 16777216 +
>a[2]::numeric * 65536 +
>
RETURN a[1]::numeric * 16777216 +
a[2]::numeric * 65536 +
a[3]::numeric * 256 +
a[4]::numeric;
END;
$$ LANGUAGE plpgsql IMMUTABLE STRICT;
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through U
, inet_aton($_[0]));
$$ LANGUAGE plperlu IMMUTABLE STRICT;
SELECT inet2num('127.0.0.1');
inet2num
2130706433
(1 row)
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
by the change. Maybe the release
notes could mention the new upper limit of factorial().
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED
turns on success, an
application wishing to check for error situations should set errno
to 0, then call strtol() or strtoll(), then check errno.
I don't know if any systems are non-compliant in this respect, but
Tom said that "we've been doing it that way (errno test only) for
many ye
4801-01-01 BC
(1 row)
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
cking *only* errno is sufficient to detect
an error. According to the standard it is.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
n doing it that way (errno test
> only) for many years without complaints. Adding a test on the return
> value is venturing into less charted waters.
Good, I'll stick with just the ERANGE check then.
--
Michael Fuhr
---(end of broadcast)---
On Wed, Nov 30, 2005 at 05:23:23PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > I usually check both in my own code but I noticed several places
> > where PostgreSQL doesn't, so I kept that style. I'll check both
> > if that's
On Wed, Nov 30, 2005 at 05:20:54PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > I'm looking at all the strtol() calls in datetime.c right now; I
> > haven't looked anywhere else yet. Should I bother checking values
> > that will be r
1 - 100 of 294 matches
Mail list logo
