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
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 thing would really be to kill the client
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
/archive/1/471541/30/0/threaded
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
resets.
In case this behavior is platform-dependent I'm testing on Solaris 9
sparc.
--
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
: 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
.
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 index scan if your joining column's datatypes
|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
---(end of broadcast
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
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
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 versions below 8.0, the planner will ignore your desire
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 broadcast
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
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 issue a warning
without failing.
--
Michael Fuhr
---(end of broadcast
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 deleted since the call to ReadDir(),
Probably
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 know the file had been
there at ReadDir
*/
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
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
.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
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 command to [EMAIL PROTECTED] so
= 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
---+--
(0,1) |1
(0,2) | 1000
(2 rows)
--
Michael Fuhr
---(end
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
subscribe-nomail command to [EMAIL
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)---
TIP 5: don't forget to increase your free
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 ;-)
--
Michael Fuhr
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://archives.postgresql.org/pgsql-patches/2006-03/msg00163.php
--
Michael Fuhr
---(end
which modules gave you trouble?
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
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
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 you recall which modules gave you trouble
://www.opengroup.org/online-pubs-short?DOC=9699959299FORM=HTML
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
? Or is there something I'm missing?
Other comments? Thanks.
--
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
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 to
choose
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
0x0025d80c in SelectConfigFiles (userDoption=0x1 Address 0x1 out of
bounds, 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 Fuhr
---(end
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?
--
Michael Fuhr
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 event type. Per discussion in pgsql
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
?
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
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. Send a patch?
Sure. Is the switch in AfterTriggerExecute
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
/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 Fuhr
---(end of broadcast
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
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 Usenet, please send an appropriate
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
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
---(end of broadcast
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 on?
--
Michael Fuhr
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 searched our list archives?
http://archives.postgresql.org
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 to [EMAIL PROTECTED] so that your
message
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 reported
The backend then loads
);
QUERY PLAN
--
Index Scan using foo_pkey, foo_pkey on foo (cost=0.00..6.03 rows=2 width=4)
Index Cond: ((id = 1) OR (id = 2))
(2 rows)
--
Michael Fuhr
.
Thanks -- I was just wondering if the behavior was expected or not.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
)
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
WHERE f1.a f2.a;
This crashes for me in 8.1.3 on FreeBSD 6.1-PRERELEASE and Solaris 9.
An assert-enabled 8.1.3 logs the following:
TRAP: BadArgument(!(((header-context) != ((void *)0)
(Node*)((header-context)))-type) == T_AllocSetContext, File:
mcxt.c, Line: 612)
--
Michael Fuhr
--
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 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 you
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 versions below 8.0, the planner will ignore your desire
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 the system is missing.
--
Michael Fuhr
---(end of broadcast)---
TIP 5: don't forget
acquire ACCESS EXCLUSIVE,
just that certain commands do. TRUNCATE isn't shown.
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
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
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 if other objects depend on the type
.
--
Michael Fuhr
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
.
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
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?
--
Michael Fuhr
. 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 versions below 8.0, the planner will ignore your desire to
choose
).
--
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
).
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
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 :-)
--
Michael Fuhr
? (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
message can get through
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
? What problem are
you trying to solve?
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
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 if your joining column's
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 broadcast)---
TIP 2
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 you searched our
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, the planner
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 this is anonymous cvs (anoncvs.postgresql.org
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
---(end of broadcast
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 posting/reading through Usenet
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;
You could also set
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
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
---(end of broadcast
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
;
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
]::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 Usenet, please
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 +
a[3]::numeric * 256
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 following it but I might have some time. Is there
a TODO list? The one I see on pgfoundry is empty.
--
Michael Fuhr
---(end of broadcast
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
') |
+---+
| 1230 |
+---+
1 row in set (0.01 sec)
--
Michael Fuhr
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
as evidence that PostgreSQL's
behavior is correct? :-)
--
Michael Fuhr
---(end of broadcast)---
TIP 6: explain analyze is your friend
.
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
choose an index scan if your joining column's datatypes do
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] so that your
message can get through
]));
$$ 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
(), 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 years without complaints.
--
Michael Fuhr
---(end of broadcast)---
TIP 2: Don't 'kill -9
On Sun, Nov 27, 2005 at 11:27:54AM -0700, Michael Fuhr wrote:
On Sun, Nov 27, 2005 at 08:45:18AM -0700, Michael Fuhr wrote:
Looks like the value is stuck at 2^31 - 1 seconds:
I see this behavior back to at least 7.3. I'd guess it's because
strtol() indicates overflow by returning LONG_MAX
On Wed, Nov 30, 2005 at 12:37:40PM -0500, Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
I see this behavior back to at least 7.3. I'd guess it's because
strtol() indicates overflow by returning LONG_MAX and setting errno
to ERANGE, but the code doesn't check
On Wed, Nov 30, 2005 at 02:01:46PM -0500, Tom Lane wrote:
Michael Fuhr [EMAIL PROTECTED] writes:
Any preferences on an approach? The simplest and easiest to verify
would be to raise an error for just this particular case; a TODO
item might be to change how the string is parsed to allow
where PostgreSQL doesn't, so I kept that style. I'll check both
if that's preferred.
--
Michael Fuhr
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so
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 range checked later anyway? Time zone
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 preferred.
I'd say not --- it's more code
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)---
TIP 9: In versions below 8.0, the planner
1 - 100 of 291 matches
Mail list logo
