On Mon, 2005-11-21 at 19:38 -0500, Andrew Dunstan wrote:
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
What I'd like to do is add an ERRORTABLE clause to COPY. The main
problem is how we detect a duplicate row violation, yet prevent it from
aborting the transaction.
Something is wrong with the web site for me. I look at:
http://www.postgresql.org/developer/
then this is what I see:
http://www.zigo.dhs.org/~dennis/tmp/dev.png
(everything is there except the main content that is not).
Turns out it's related to the ads, so if I just adblock the ad
[moved to -www]
Something is wrong with the web site for me. I look at:
http://www.postgresql.org/developer/
then this is what I see:
http://www.zigo.dhs.org/~dennis/tmp/dev.png
(everything is there except the main content that is not).
Yikes.
Turns out it's related to the
On Tue, 22 Nov 2005, Magnus Hagander wrote:
Turns out it's related to the ads, so if I just adblock the
ad server I can see the page just fine. Kind of bad it's
needed however :-)
I also tried to show the page in opera and it looks the same
as in firefox.
Intersting. It works
On Tue, 22 Nov 2005, Dennis Bjorklund wrote:
ps. The cvs server also seems to be down (postgresql.org).
Forgot to say in the last mail, but this also works now. Seems like I
should have waited some more before sending the mail. I waited 30 minutes
but I should have waited 40...
--
/Dennis
With AIX 5, the easiest way to get a shared object is to pass
-bexpall
to the linker. This results in all symbols being exported.
Yes, that is another reason not to use this broken switch.
And last time I checked (AIX 4.3.3), -bexpall did not export all needed
symbols
(e.g. globals) from the
On Tue, 2005-11-22 at 10:00 +0800, Christopher Kings-Lynne wrote:
Seems similar to the pgloader project on pgfoundry.org.
It is similar and good, but I regard that as a workaround rather than
the way forward.
Best Regards, Simon Riggs
---(end of
On Mon, 2005-11-21 at 19:05 -0500, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Flow of control would be to:
locate page of index where value should go
lock index block
_bt_check_unique, but don't error
if violation then insert row into ERRORTABLE
Just out of curiosity. Is there someone involved with ToDo item %Allow
pg_hba.conf settings to be controlled via SQL?
Regards,
Gevik.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Tue, Nov 22, 2005 at 10:07:15AM +0100, Zeugswetter Andreas DCP SD wrote:
PS: I'd prefer if readline was only linked where it is needed, namely in
psql.
The problem as stated is that people don't want to maintain lists of
libraries as needed by each program, so we link all of them.
Since it
On Tue, Nov 22, 2005 at 09:22:18AM +0100, Dennis Bjorklund wrote:
Something is wrong with the web site for me. I look at:
http://www.postgresql.org/developer/
snip
Turns out it's related to the ads, so if I just adblock the ad server I
can see the page just fine. Kind of bad it's needed
On Tue, 22 Nov 2005, Dennis Bjorklund wrote:
On Tue, 22 Nov 2005, Dennis Bjorklund wrote:
ps. The cvs server also seems to be down (postgresql.org).
Forgot to say in the last mail, but this also works now. Seems like I
should have waited some more before sending the mail. I waited 30
I've noticed that in 8.1 the output of SHOW ALL includes a description
column. This makes the output very wide which makes it hard to use from
psql (I need to make the terminal window 164 characters wide to not get
any line wrapping). I wish I would have noticed this before 8.0 was out
and then I
On Tue, Nov 22, 2005 at 04:20:12AM +0100, Petr Jelinek wrote:
It was already said here that oracle and db2 both use MERGE, dunno about
mssql.
And yes merge CAN be used to do REPLACE (oracle uses their dummy table
for this, we can use the fact that FROM clause isn't required in postgres).
I apologise if this isn't the correct list to post this issue to, I just
wanted to give a heads up that the main postgresql.org website doesn't
seem to be giving access to any ftp mirrors. Needless to say, when I
tried to download what I was after from the main server, I just got a
'too many
Take the query.
select a,b from dupa where b::text in (select b::text from dupa group by
b::text having count(b) 2);
This is acceptable to create a unique constraint, however, we cannot mark
the column unique, without defining btree operators, which clearly are not
possible for sorting. Is
Kevin McArthur [EMAIL PROTECTED] writes:
This is acceptable to create a unique constraint, however, we cannot mark
the column unique, without defining btree operators, which clearly are not
possible for sorting. Is there any way to base the operators based on the
text representation of the
Simon Riggs [EMAIL PROTECTED] writes:
I have committed the sin of omission again.
Duplicate row violation is the big challenge, but not the only function
planned. Formatting errors occur much more frequently, so yes we'd want
to log all of that too. And yes, it would be done in the way you
On 2005-11-22, at 15:45, Tom Lane wrote:
Kevin McArthur [EMAIL PROTECTED] writes:
This is acceptable to create a unique constraint, however, we
cannot mark
the column unique, without defining btree operators, which clearly
are not
possible for sorting. Is there any way to base the
On Tue, Nov 22, 2005 at 09:58:44AM -0500, Tom Lane wrote:
The general problem that needs to be solved is trap any error that
occurs during attempted insertion of a COPY row, and instead of aborting
the copy, record the data and the error message someplace else. Seen
in that light,
On Tue, Nov 22, 2005 at 04:24:21PM +0100, Grzegorz Jaskiewicz wrote:
Translation: you do know how to define a sortable order (ie, generate
the text version and compare); you're just too lazy to create the
operators to do it ...
We do have WORKING , , etc operators, and ::text cast already.
Martijn van Oosterhout kleptog@svana.org writes:
On Tue, Nov 22, 2005 at 09:58:44AM -0500, Tom Lane wrote:
The general problem that needs to be solved is trap any error that
occurs during attempted insertion of a COPY row, and instead of aborting
the copy, record the data and the error message
On Tue, 22 Nov 2005, Grzegorz Jaskiewicz wrote:
Thing is, can I have btree and gist indexes at the same time ?
no, we have contrib/btree_gist for this
Regards,
Oleg
_
Oleg Bartunov, sci.researcher, hostmaster
On Tue, Nov 22, 2005 at 10:57:19 +0100,
[EMAIL PROTECTED] wrote:
Just out of curiosity. Is there someone involved with ToDo item %Allow
pg_hba.conf settings to be controlled via SQL?
I don't remember any discussions about this recently, so I doubt it is being
actively worked on right now.
On Tue, Nov 22, 2005 at 10:45:50AM -0500, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
Actually, there are really only a few errors people want to trap I
imagine:
You've forgotten bad data, eg foo in an integer field, or an
untranslatable multibyte character. The
On 2005-11-22, at 16:39, Martijn van Oosterhout wrote:
On Tue, Nov 22, 2005 at 04:24:21PM +0100, Grzegorz Jaskiewicz wrote:
Translation: you do know how to define a sortable order (ie,
generate
the text version and compare); you're just too lazy to create the
operators to do it ...
We do
On Tue, Nov 22, 2005 at 05:14:35PM +0100, Grzegorz Jaskiewicz wrote:
Ok, I hacked btree for my type, and surely I can have both btree and
gist at the same time on the same column.
/me is now going to have a look on btree_gist.
You don't actually have to have a btree defined on your column
Bruno Wolff III wrote:
On Tue, Nov 22, 2005 at 10:57:19 +0100,
[EMAIL PROTECTED] wrote:
Just out of curiosity. Is there someone involved with ToDo item “%Allow
pg_hba.conf settings to be controlled via SQL”?
pgAdmin with the admin81 functions can handle this...
Regards,
Andreas
Tom Lane [EMAIL PROTECTED] writes:
Martijn van Oosterhout kleptog@svana.org writes:
On Tue, Nov 22, 2005 at 09:58:44AM -0500, Tom Lane wrote:
The general problem that needs to be solved is trap any error that
occurs during attempted insertion of a COPY row, and instead of aborting
the
On 2005-11-22, at 17:17, Martijn van Oosterhout wrote:
On Tue, Nov 22, 2005 at 05:14:35PM +0100, Grzegorz Jaskiewicz wrote:
Ok, I hacked btree for my type, and surely I can have both btree and
gist at the same time on the same column.
/me is now going to have a look on btree_gist.
You don't
I found this thread on google,
http://groups.google.nl/group/pgsql.hackers/browse_thread/thread/1ccb7ade8d7e7475/8b10fb1ca5fdd3ef?lnk=stq=pg_hba.conf+settings+to+be+controlled+via+SQLrnum=3hl=nl#8b10fb1ca5fdd3ef
Bruno Wolff III wrote:
On Tue, Nov 22, 2005 at 10:57:19 +0100,
[EMAIL
Bob Ippolito [EMAIL PROTECTED] writes:
On Nov 21, 2005, at 5:50 PM, Tom Lane wrote:
Hm, do the drop/add constraint functions get executed even when
clone_table decides not to make a new table? If so, that would
probably explain the pattern I'm seeing in the dump of many updates of the
Greg Stark [EMAIL PROTECTED] writes:
I think that's precisely the point here though. There are basically two
categories of errors:
1) Data that can be parsed and loaded but generates some sort of constraint
violation such as a UNIQUE violation, foreign key violation, or other
Sorry for this late answer. I tried a lot of things and it still doesn't work.
2005/11/11, Martijn van Oosterhout kleptog@svana.org:
On Thu, Nov 10, 2005 at 11:53:04PM +0100, Guillaume LELARGE wrote:
Hi,
I've installed a 8.1.0 PostgreSQL server on a SCO OpenServer 5.0.6. It
seemed to
Tom Lane [EMAIL PROTECTED] writes:
It would be nice to be able to have the former loaded into an actual table
where it can be queried and perhaps fixed and reloaded.
The latter clearly cannot.
Sure it can --- you just have to dump it as raw text (or perhaps bytea,
as someone suggested
Guillaume Lelarge [EMAIL PROTECTED] writes:
I've installed a 8.1.0 PostgreSQL server on a SCO OpenServer 5.0.6.
Some tests failed.. strangely, it seems int4 and int8 share the same
range.
This is expected behavior if the platform's C compiler doesn't support
any 64-bit integer type. We go
On Tue, Nov 22, 2005 at 12:16:00PM -0500, Tom Lane wrote:
I think the distinction you are proposing between constraint errors
and datatype errors is entirely artificial. Who's to say what is a
constraint error and what is a datatype error, especially when you
start thinking about cases like
Sorry for answering this late.
2005/11/16, Larry Rosenman ler@lerctr.org:
Bruce Momjian wrote:
The SCO compiler is so buggy (and for so many years) I see no reason
to even look at a bug report from someone using it.
I **REALLY** wish you would STOP saying that, Bruce. The current
Gavin Sherry wrote:
Related question: are there plans afoot to allow specifying an alternate
location for pg_xlog (or pg_delete-me-not) to save doing the shutdown-DB, mv
directory to other disk, symlink, start-DB dance?
People have discussed it but I don't know of anyone working on it.
I have update the first section of the FAQ:
http://www.postgresql.org/docs/faqs.FAQ.html
In particular:
o reordered items to be more logical
o added clarification of license
o added section about bug reporting replies
o added section of feature
Jaime Casanova wrote:
And yes merge CAN be used to do REPLACE (oracle uses their dummy table
for this, we can use the fact that FROM clause isn't required in postgres).
the FROM clause is required by default (starting with 8.1) unless you
change a postgresql.conf parameter.
and i
On 11/22/05, Bruce Momjian pgman@candle.pha.pa.us wrote:
Jaime Casanova wrote:
And yes merge CAN be used to do REPLACE (oracle uses their dummy table
for this, we can use the fact that FROM clause isn't required in
postgres).
the FROM clause is required by default (starting
On Mon, Nov 21, 2005 at 08:40:38PM -0500, Tom Lane wrote:
You should find out what the problem is before you start writing
documentation about it ;-). This has nothing whatever to do with
bigint.
Damn, there's 5 minutes of my life that I won't get back! ;P
snip
What the code is trying to do
On Tue, Nov 22, 2005 at 11:57:48AM +0100, Martijn van Oosterhout wrote:
excellent research snipped
Rather than trying to make MERGE do something it wasn't designed for,
we should probably be spending our efforts on triggers for error
conditions. Maybe something like:
CREATE TRIGGER foo
On Fri, Nov 18, 2005 at 09:03:25PM +0100, Martijn van Oosterhout wrote:
I'd say implement SQL MERGE which doesn't have any really unusual
features. And seperately implement some kind of INSERT OR UPDATE which
works only for a table with a primary key.
Is there any reeason this has to be a PK;
On Mon, Nov 21, 2005 at 09:14:33PM +0100, Marcus Engene wrote:
Jim C. Nasby wrote:
It might be more useful to look at caching only planning and not
parsing. I'm not familiar with the output of the parsing stage, but
perhaps that could be hashed to use as a lookup into a cache of planned
Tom Lane wrote:
I see Alvaro and Andrew have landed the patches they were working on
last week, so maybe today is a good time to do that re-pgindent we
were discussing.
Done.
--
Bruce Momjian| http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610)
Since we were breaking our usual rule by re-indenting the 8.1 branch,
I took the time to eyeball the whole cvs diff for changes that weren't
just comment block fixes. I found a few things that need attention.
This change is disturbing first because it seems completely unnecessary,
and second
Gregory Maxwell wrote:
On 11/21/05, Jim C. Nasby [EMAIL PROTECTED] wrote:
What about Greg Stark's idea of combining Simon's idea of storing
per-heap-block xmin/xmax with using that information in an index scan?
ISTM that's the best of everything that's been presented: it allows for
faster
[EMAIL PROTECTED] wrote:
On Fri, Nov 18, 2005 at 03:46:42PM +, Richard Huxton wrote:
Simon Riggs wrote:
One of the major complaints is always Select count(*) is slow.
Although there seem to have been plenty of ideas on this they all seem
to just provide a solution for the whole table
Jim C. Nasby wrote:
On Fri, Nov 18, 2005 at 02:56:52PM -0500, Gregory Maxwell wrote:
However, some great ideas have been proposed here which would not only
help in that case but would otherwise be quite useful.
*Inclusion of a 'MVCC inflight' bit in indexes which would allow
skipping
Jaime Casanova wrote:
the FROM clause is required by default (starting with 8.1) unless you
change a postgresql.conf parameter.
and i don't think that idea will have any fan...
Bruce already replied to your first statement so, what idea won't have
any fan ? It's not that we would change
Sorry for the top post. If you can get a UDK license, that will work
better.
LER
On Nov 22, 2005, at 12:02 PM, Guillaume Lelarge wrote:
Sorry for answering this late.
2005/11/16, Larry Rosenman ler@lerctr.org:
Bruce Momjian wrote:
The SCO compiler is so buggy (and for so many years) I
On Tue, Nov 22, 2005 at 06:11:01PM -0500, Bruce Momjian wrote:
[EMAIL PROTECTED] wrote:
Jan has been talking about have a bitmap to track pages that need
vacuuming, and I am wondering if the same system could be used to track
the heap-dirty bits. Putting one bit on every 8k disk page means we
On Tue, Nov 22, 2005 at 01:38:34PM -0500, Bruce Momjian wrote:
Gavin Sherry wrote:
Related question: are there plans afoot to allow specifying an alternate
location for pg_xlog (or pg_delete-me-not) to save doing the shutdown-DB,
mv
directory to other disk, symlink, start-DB dance?
On Tue, 22 Nov 2005, Jim C. Nasby wrote:
On Tue, Nov 22, 2005 at 01:38:34PM -0500, Bruce Momjian wrote:
Gavin Sherry wrote:
Related question: are there plans afoot to allow specifying an alternate
location for pg_xlog (or pg_delete-me-not) to save doing the
shutdown-DB, mv
Tom Lane wrote:
Since we were breaking our usual rule by re-indenting the 8.1 branch,
I took the time to eyeball the whole cvs diff for changes that weren't
just comment block fixes. I found a few things that need attention.
This change is disturbing first because it seems completely
Bruce Momjian wrote:
And what happened here?
I saw this one to and was stumped at the cause. We have other 'typedef
enum' lines in the code which were not mangled, just this one. Again,
needs research.
Index: src/interfaces/libpq/libpq-fe.h
***
*** 35,41
Jim C. Nasby wrote:
On Tue, Nov 22, 2005 at 01:38:34PM -0500, Bruce Momjian wrote:
* Allow the pg_xlog directory location to be specified during initdb
with a symlink back to the /data location
I think the only reason it is not done yet is because it is so easy to
do for
Another vote for libedit support... We at Greenplum definitely want to
use it.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Tue, Nov 22, 2005 at 06:11:01PM -0500, Bruce Momjian wrote:
[EMAIL PROTECTED] wrote:
A solution enhancing the above mentioned indexes, to maintain a count
for whole index blocks, would allow whole index blocks that satisfy
the WHERE clause to be counted, assuming the whole index block is
On Wed, 23 Nov 2005 11:23 am, Gavin Sherry wrote:
Along those lines, is there anything else that would benefit from being
moved? pg_clog and pg_subtrans come to mind; but maybe pg_multixact and
pg_twophase are candidates as well?
pgsql_tmp
Does anyone have any recommendations about which
Larry Rosenman wrote:
Sorry for the top post. If you can get a UDK license, that will work
better.
Oh, so one gets a buggy compiler by default and has to pay for a better
one? Cool! I'm drooling already, I want one of those SCO things, where
do I get it? Pity those GCC guys, having only
On Nov 22, 2005, at 7:04 PM, Alvaro Herrera wrote:
Larry Rosenman wrote:
Sorry for the top post. If you can get a UDK license, that will work
better.
Oh, so one gets a buggy compiler by default and has to pay for a
better
one? Cool! I'm drooling already, I want one of those SCO things,
Here are some little changes to the postgreSQL server backend I found
beeing convenient for me
while I was attempting to get interoparability with a binary only
program. The patch attached is tested and works
for 8.0.0beta3.
The so called big ones under these DBMS eat the following kind of
I **REALLY** wish you would STOP saying that, Bruce. The current OpenServer
Compiler (UDK), is the same as on UnixWare, and is **MUCH** better than the
Old SVR3 compiler.
We **REALLY** **SHOULD** look at it.
Well actually no, we shouldn't. Regardless of the technical good or
bad.. We
Chuck McDevitt wrote:
Another vote for libedit support... We at Greenplum definitely want to
use it.
If we are going to move toward libedit then libedit should be included
in core. Otherwise
you are creating a dependency on the largest postgresql used OS (linux).
The advantage
here of
Wolfgang [EMAIL PROTECTED] writes:
Here are some little changes to the postgreSQL server backend I found
beeing convenient for me
You don't seriously expect any of this to get applied, do you?
nullstr0 reverts a deliberate change made in PG 7.3. It's way past
time to be complaining about
Joshua D. Drake [EMAIL PROTECTED] writes:
If we are going to move toward libedit then libedit should be included
in core.
We already do support libedit; support does not mean include, for
either readline or libedit.
I think it'd be reasonable to provide a configure option to control
selection
Alvaro Herrera [EMAIL PROTECTED] writes:
Jim C. Nasby wrote:
Along those lines, is there anything else that would benefit from being
moved? pg_clog and pg_subtrans come to mind; but maybe pg_multixact and
pg_twophase are candidates as well?
Hmm, I doubt moving any of the SLRU files (clog,
Seems similar to the pgloader project on pgfoundry.org.
It is similar and good, but I regard that as a workaround rather than
the way forward.
Yes, your way would be rad :)
---(end of broadcast)---
TIP 1: if posting/reading through Usenet,
Actually, there are really only a few errors people want to trap I
imagine:
- CHECK constraints (all handled in ExecConstraints)
- Duplicate keys
- Foreign key violations (all handled by triggers)
Rather than worry about all the events we can't safely trap, how about
we simply deal with the
Bruce Momjian wrote:
Tom Lane wrote:
Since we were breaking our usual rule by re-indenting the 8.1 branch,
I took the time to eyeball the whole cvs diff for changes that weren't
just comment block fixes. I found a few things that need attention.
This change is disturbing first because
2005/11/23, Joshua D. Drake [EMAIL PROTECTED]:
I **REALLY** wish you would STOP saying that, Bruce. The current OpenServer
Compiler (UDK), is the same as on UnixWare, and is **MUCH** better than the
Old SVR3 compiler.
We **REALLY** **SHOULD** look at it.
Well actually no, we
74 matches
Mail list logo
