Hi,
attached are two patches against HEAD. The smaller one is meant to be
commited - it adds some functions that manipulate double-linked lists,
namely inserting a new cell after or before another cell and swapping
two adjacent cells. It felt like being back in the first year of
studies. I
On Sat, 2008-03-22 at 22:40 +0200, Mihai Criveti wrote:
I am trying to build PostgreSQL 8.3.1 on OpenVMS 8.3 Alpha, patched to
UPDATE v6.0 ECO:
DEC AXPVMS VMS83A_UPDATE V6.0Patch Install Val
14-MAR-2008
Using the HP C compilers:
HP C Version 7.3 for OpenVMS Alpha Systems
On Thu, 2008-06-26 at 13:42 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
We can check for removal of a rel by
1. inspecting the target list for the query to see if there are rels
that do not provide any attributes. (We might also use equivalence
classes to recode the
Bruce Momjian wrote:
Tom Lane wrote:
...
* no permanent archive of the submitted patch
* reviewer won't know if the submitter changes the patch after he
downloads a copy, and in fact nobody will ever know unless the submitter
takes the time to compare the eventual commit to what he thinks
When we move from having a virtual xid to having a real xid I don't see
any attempt to re-arrange the lock queues. Surely if there are people
waiting on the virtual xid, they must be moved across to wait on the
actual xid? Otherwise the locking queue will not be respected because we
have two
On Thu, 2008-06-26 at 18:53 -0400, Bruce Momjian wrote:
David Fetter wrote:
Folks,
When I do CREATE TABLE foo(LIKE bar INCLUDING CONSTRAINTS), it doesn't
include foreign key constraints (8.3.1). I believe this is surprising
behavior, but maybe not a bug, so I'd like to propose
Michael Meskes wrote:
On Wed, Jun 18, 2008 at 09:26:24PM -0400, Tom Lane wrote:
Makefile.shlib builds these in the distprep action, so I suppose
they're supposed to be there. libpq .cvsignore's its equivalent
files, so I'd agree with doing that. It looks like there should be
three such
Is it desirable that pg_dump doesn't dump config settings set via ALTER
DATABASE?
http://archives.postgresql.org/pgsql-novice/2008-04/msg00016.php
I just got bitten by a DateStyle not being restored on my test DB (I
usually set it client-side in the app). I could see someone without my
steel
Alvaro Herrera [EMAIL PROTECTED] writes:
If only VACUUM is going to set flexible to off, maybe it's better to
leave the APIs as they are and have a global that's set by VACUUM only
(and reset in a PG_CATCH block).
Ugh. Perhaps it would be simpler to have a wrapper function HTSV() macro which
Simon Riggs [EMAIL PROTECTED] writes:
The default and minimum value for this parameter is 1, so very similar to
existing behaviour. Expected settings would be 2-5, possibly as high as 20,
though those are just educated guesses. So the maximum is set arbitrarily as
100.
Not a fan of arbitrary
On Fri, Jun 27, 2008 at 08:56:11AM -0400, Alvaro Herrera wrote:
There are three -- two of them are .cvsignore'd. Should we just
.cvsignore the third one, or remove it from the build, or ...?
I'd say so.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot
Richard Huxton [EMAIL PROTECTED] writes:
Is it desirable that pg_dump doesn't dump config settings set via ALTER
DATABASE?
Well, it's intentional anyway: that's handled by pg_dumpall. The basic
design is that anything that can be seen from outside a specific
database is handled on the
On Fri, 2008-06-27 at 15:25 +0100, Gregory Stark wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
If only VACUUM is going to set flexible to off, maybe it's better to
leave the APIs as they are and have a global that's set by VACUUM only
(and reset in a PG_CATCH block).
Ugh. Perhaps it
Hello Hiroshi-san,
Your new win32.mak causes the following error with MSVC 2003:
Creating library .\Release\libpqdll.lib and object .\Release
\libpqdll.exp
mt -manifest .\Release\libpq.dll.manifest -outputresource:.
\Release\libp
q.dll;2
Microsoft (R) Manifest Tool version
On Fri, 2008-06-27 at 15:36 +0100, Gregory Stark wrote:
Simon Riggs [EMAIL PROTECTED] writes:
The default and minimum value for this parameter is 1, so very similar to
existing behaviour. Expected settings would be 2-5, possibly as high as 20,
though those are just educated guesses. So
Hi Jeff-san.
Uga,,, Ok.
Please try this.
Thanks your perseverance. !!
Regards,
Hiroshi Saito
- Original Message -
From: Jeff McKenna [EMAIL PROTECTED]
Hello Hiroshi-san,
Your new win32.mak causes the following error with MSVC 2003:
Creating library .\Release\libpqdll.lib and
Tom Lane wrote:
Richard Huxton [EMAIL PROTECTED] writes:
Is it desirable that pg_dump doesn't dump config settings set via ALTER
DATABASE?
Well, it's intentional anyway: that's handled by pg_dumpall. The basic
design is that anything that can be seen from outside a specific
database is
Simon Riggs wrote:
When we move from having a virtual xid to having a real xid I don't
see any attempt to re-arrange the lock queues. Surely if there are
people waiting on the virtual xid, they must be moved across to wait
on the actual xid? Otherwise the locking queue will not be respected
This thread
http://archives.postgresql.org/pgsql-hackers/2008-01/msg00134.php
kind of wandered off into the weeds after identifying a semi-related
bug in CLUSTER, but the original problem still remains: if a backend
crashes after creating some temp tables, the tables remain present.
Such tables
Ooops, I am sorry so that it may be spam. ...
I have noticed, although there were few conditions.
pass the VC6,VC7,VC71
Regards,
Hiroshi Saito
- Original Message -
From: Hiroshi Saito [EMAIL PROTECTED]
Hi Jeff-san.
Uga,,, Ok.
Please try this.
Thanks your perseverance. !!
Gregory Stark wrote:
I'm also a bit concerned that *how many hint bits* isn't enough information to
determine how important it is to write out the page.
Agreed, that doesn't seem like a very good metric to me either.
Or how many *unhinted* xmin/xmax
values were found? If HTSV can hint xmin
Tom Lane [EMAIL PROTECTED] writes:
The main attractions of this idea are avoiding the corrupt-index issue and
not doing vacuuming work that's 99.99% sure to be useless.
It does seem strange to me to vacuum a table you're pretty sure is useless
*and* quite likely corrupt.
Could autovacuum emit
Hiroshi-san,
All win32 parts have been built!
That last file that you sent worked with MSVC 2003, and libpq.dll was
successfully built. Thank you very much for fixing this for me. Will
this be committed to CVS head for others?
---
Jeff McKenna
FOSS4G Consulting and Training Services
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
On Thu, 2008-06-26 at 12:36 -0400, Robert Haas wrote:
It's my understanding that the philosophy of the PGDG in the past has
been to avoid putting any kind of hints into the system, focusing
rather an improving the planning of queries.
Tom Lane wrote:
Another issue is that leftover temp tables would be significantly more
likely to be self-inconsistent than normal tables, since operations on
them are not WAL-logged and it's entirely likely that the owning backend
crashed with some dirty pages not written out from its local
Hi Jeff-san.
Thanks!!
The version which you use is supported officially.
http://www.postgresql.org/docs/8.3/static/install-win32-libpq.html
To build the libpq client library using Visual Studio 7.1 or later.
However, adjustment may be necessity.
I will propose patch.!
Regards,
Hiroshi Saito
Gregory Stark [EMAIL PROTECTED] writes:
Could autovacuum emit log messages as soon as it sees such tables and start
dropping them at some point later?
We might have to rearrange the logic a bit to make that happen (I'm not
sure what order things get tested in), but a log message does seem like
* Tom Lane ([EMAIL PROTECTED]) wrote:
The only solution proposed in that thread was to auto-delete temp
tables at postmaster restart; which I opposed on the grounds that
throwing away data right after a crash was a terrible idea from a
forensic standpoint.
Why not just rename the files out of
Stephen Frost [EMAIL PROTECTED] writes:
* Tom Lane ([EMAIL PROTECTED]) wrote:
The only solution proposed in that thread was to auto-delete temp
tables at postmaster restart; which I opposed on the grounds that
throwing away data right after a crash was a terrible idea from a
forensic
Stephen Frost wrote:
* Tom Lane ([EMAIL PROTECTED]) wrote:
The only solution proposed in that thread was to auto-delete temp
tables at postmaster restart; which I opposed on the grounds that
throwing away data right after a crash was a terrible idea from a
forensic standpoint.
Why not
Richard Huxton wrote:
At present it means you can't reliably do:
DROP DATABASE foo;
pg_restore --create foo.dump
I'd then have to either hand edit the dumpall dump or wade through a
bunch of errors checking that none of them were relevant.
Actually, I'm not sure pg_dumpall does them either.
Richard Huxton wrote:
Richard Huxton wrote:
At present it means you can't reliably do:
DROP DATABASE foo;
pg_restore --create foo.dump
I'd then have to either hand edit the dumpall dump or wade through a
bunch of errors checking that none of them were relevant.
Actually, I'm not sure
Tom Lane wrote:
Gregory Stark [EMAIL PROTECTED] writes:
Could autovacuum emit log messages as soon as it sees such tables and start
dropping them at some point later?
We might have to rearrange the logic a bit to make that happen (I'm not
sure what order things get tested in), but a log
Heikki Linnakangas wrote:
Or we could have autovacuum just drop orphaned temp tables, *if*
they have gotten old enough to need anti-wraparound vacuuming.
While I'm still uncomfortable with having autovac drop anything,
at least this would avoid the worst cases of gee I really needed
that data
On Jun 26, 2008, at 13:59, Tom Lane wrote:
David E. Wheeler [EMAIL PROTECTED] writes:
So, are your certain about this?
See Turkish --- in that locale i and I are not an upper/lower pair,
instead they pair with some non-ASCII letters. There are likely
other cases but that's the
Jan Urbański wrote:
I'll add the first one to the commit fest page, and I'm sending it to
-hackers with congratulations on the decision to ditch -patches ;)
Hm... someone apparently added this mail to the wiki pag independently
of me, so there were two duplicate entries. I found the second
Jan,
Hm... someone apparently added this mail to the wiki pag independently
of me, so there were two duplicate entries. I found the second
description better, so I removed my original entry and left the other
one.
Yeah, I've been going through -hackers and -patches and adding stuff to the
Simon Riggs [EMAIL PROTECTED] writes:
On Thu, 2008-06-26 at 13:42 -0400, Tom Lane wrote:
It might be possible to treat ignore the RHS as a join strategy and
try to apply it while forming join relations, which would be late enough
to have all the needed info available.
Oh, actually have a
Dear friends,
You may know me as I worked a long time ago on pgAdmin I with Dave.
As this is an XML related question and XML is quite new, I am posting
on hackers ML. If any solution is being developped, please inform us.
We would like to develop a free REST database (real-estate standard)
Dear friends,
You may know me as I worked a long time ago on pgAdmin I with Dave.
As this is an XML related question and XML is quite new, I am posting
on hackers ML.
We would like to develop a free REST database (real-estate standard)
based on a PostgreSQL schema. This is a free solution for
Simon Riggs [EMAIL PROTECTED] writes:
In cases where we know we will assign a real xid, can we just skip the
assignment of the virtual xid completely?
Even if we could do this I doubt it would be a good idea. It'd destroy
the invariant that all transactions have a vxid, which at the very least
Simon Riggs [EMAIL PROTECTED] writes:
On Thu, 2008-06-26 at 18:53 -0400, Bruce Momjian wrote:
TODO has:
o Allow inherited tables to inherit indexes, UNIQUE constraints,
and primary/foreign keys
But that TODO item is about inheritance, which has approximately
zip to do with CREATE TABLE
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
We might have to rearrange the logic a bit to make that happen (I'm not
sure what order things get tested in), but a log message does seem like
a good idea. I'd go for logging anytime an orphaned table is seen,
and dropping once it's
On Wed, Jun 25, 2008 at 9:57 AM, Andrew Hammond
[EMAIL PROTECTED] wrote:
On Wed, Jun 25, 2008 at 2:58 AM, Heikki Linnakangas [EMAIL PROTECTED] wrote:
Andrew Hammond wrote:
I found this error message in my log files repeatedly:
Error: failed to re-find parent key in
Tom Lane wrote:
We might have to rearrange the logic a bit to make that happen (I'm not
sure what order things get tested in), but a log message does seem like
a good idea. I'd go for logging anytime an orphaned table is seen,
and dropping once it's past the anti-wraparound horizon.
Is there
Tom Lane writes:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
We might have to rearrange the logic a bit to make that happen
(I'm not
sure what order things get tested in), but a log message does seem
like
a good idea. I'd go for logging anytime an orphaned table is seen,
and
Howdy,
[N.B.: I tried to send this a while ago but it didn't get delivered,
I'm assuming because, with the uncompressed patch, the email was too
big for -hackers. So this is a re-send with the patch gzip'd. Sorry
for any duplication].
Please find attached a patch adding a locale-aware,
Matthew T. O'Connor [EMAIL PROTECTED] writes:
Is there an easy way for an Admin clean-up the lost temp tables that
autovacuum is complaining about? It seems like it could be along time
and a lot of log messages between when they are first orphaned and and
finally dropped due to
Andrew Hammond [EMAIL PROTECTED] writes:
(I thought this line was interesting)
Jun 27 15:54:31 qadb2 postgres[92519]: [44-1] PANIC: could not open
relation 1663/16386/679439393: No such file or directory
I googled to find out what the numbers 1663/16386/679439393 from the
PANIC message
Jean-Michel,
As this is an XML related question and XML is quite new, I am posting
on hackers ML. If any solution is being developped, please inform us.
How is it XML-related?
We would like to develop a free REST database (real-estate standard)
based on a PostgreSQL schema. This is a free
Josh Berkus [EMAIL PROTECTED] writes:
Well, anything based on XML data is going to be pretty slow. There's just no
way to extra data from an XML field without lots of parsing.
I thought there'd been some discussion of storing XML data values in
some kind of pre-parsed format?
I agree that's
On Fri, 27 Jun 2008, Jean-Michel Pour? wrote:
Dear friends,
You may know me as I worked a long time ago on pgAdmin I with Dave.
ЪЪAs this is an XML related question and XML is quite new, I am posting
on hackers ML. If any solution is being developped, please inform us.
We would like to
52 matches
Mail list logo
