Being able to export to other dbs will get us _more_ users, not less.
Without some type of corresponding import utility that seems logically false.
Nope. Consider it like this. How many companies are going to move to
PostgreSQL from Oracle if they cannot dump their data back to Oracle as
a
Hello, dump problems again.
I'm working on a dump ToC parser for spatial database restore
(postgis).
I've noticed that pg_dump-7.3 and pg_dump-7.4 list CAST entries
in different ways. Still 'Dump Version' is the same (1.7-0).
What does 'Dump Version' refer to then ? Are these ToC output
changes
At 08:09 PM 13/08/2004, strk wrote:
What does 'Dump Version' refer to then ? Are these ToC output
changes encoded somehow ?
The file format version of pg_dump; the actual contents depend on pg_dump
version, and the source database since pg_dump asks the source (as much as
possible) to present
On Fri, Aug 13, 2004 at 08:42:44PM +1000, Philip Warner wrote:
At 08:09 PM 13/08/2004, strk wrote:
What does 'Dump Version' refer to then ? Are these ToC output
changes encoded somehow ?
The file format version of pg_dump; the actual contents depend on pg_dump
version, and the source
In backend/commands/trigger.c the following can be found:
/*
* Trigger protocol allows function to return a null pointer,
* but NOT to set the isnull result flag.
*/
if (fcinfo.isnull)
ereport(ERROR,
Why?
Regards,
Thomas Hallgren
---(end of
At 08:53 PM 13/08/2004, strk wrote:
Commenting out lines from the dump corresponding to objects that
will be defined by another script.
I may have misunderstood, but try:
pg_restore -l dumpfile listfile
then delete lines from listfile that you do not want, and do:
pg_restore -L listfile
[redirecting]
I have abstracted this problem, and we definitely have a newline bug
that has to be fixed, IMNSHO.
Attached are 2 scripts that are identical except that one has DOS-style
line endings and one has Unix style line endings. The DOS-style just
fails miserably with no warning. It's
hackers,
attached you may find another bunch of translated strings.
Cheers
Zoltan
pgscripts-sk.po.bz2
Description: BZip2 compressed data
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Philip, I'm trying to make the process you describe automatic.
A script reads objects definitoin from an .sql file
and automatically deletes linkes from 'listfile' corresponding
to objects already found in the given .sql file.
As for my problem (detecting CASTS) I had to support
lines in the
Andrew Dunstan wrote:
The attached patch appears to solve the problem. However, while it
makes us conform to the first sentence below from the docs, it doesn't
comply with the second. Not sure what to do about that. Maybe there's
a better solution?
Attached patch seems much better, I think.
hackers,
here goes the last missing bunch of strings translated to sk.
Cheers
Zoltan
pg_resetxlog-sk.po.bz2
Description: BZip2 compressed data
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
At 10:30 PM 13/08/2004, strk wrote:
From PG73:
552; 2663984 CAST bytea (public.wkb)
From PG74:
547; 1915318 CAST CAST (public.wkb AS bytea)
Since these two dumps have same file format version I asked..
The file format (unfortunately for you) does not define the format of the
On Fri, Aug 13, 2004 at 11:12:50PM +1000, Philip Warner wrote:
At 10:30 PM 13/08/2004, strk wrote:
From PG73:
552; 2663984 CAST bytea (public.wkb)
From PG74:
547; 1915318 CAST CAST (public.wkb AS bytea)
Since these two dumps have same file format version I asked..
The
Thomas Hallgren [EMAIL PROTECTED] writes:
In backend/commands/trigger.c the following can be found:
/*
* Trigger protocol allows function to return a null pointer,
* but NOT to set the isnull result flag.
*/
if (fcinfo.isnull)
ereport(ERROR,
Why?
Why
Someone on IRC just reported this to_char() failure with negative
intervals:
test= SELECT to_char('-00:17:56.886375'::interval, 'HH24:MI:SS');
to_char
--
00:-1:-5
(1 row)
Looks like a bug to me. :-)
--
Bruce Momjian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm having some spare time and I'm testing what Tom Lane was
suggesting:
===
Tom Lane wrote:
1. You set up WAL archiving on the master, and arrange to ship copies of
Oops! [EMAIL PROTECTED] (Reinoud van Leeuwen) was seen spray-painting on a wall:
On Mon, Aug 09, 2004 at 09:30:09AM +0200, Peter Eisentraut wrote:
Tom Lane wrote:
I haven't seen any particular reason why we should adopt another SCM.
Perhaps BitKeeper or SubVersion would be better for our
Hi list,
i tried a bit with errorhandling and found the following :
(i want to ignore the dublicate key exception)
CREATE OR REPLACE FUNCTION test() RETURNS VARCHAR AS'
BEGIN
BEGIN
INSERT INTO table a dublicate key (primary);
EXCEPTION
WHEN OTHERS THEN ROLLBACK;
END;
RETURN ''test'';
Regression tests on PostgreSQL 8 Beta are successful.
[EMAIL PROTECTED] regress]$ cat /etc/redhat-release
Red Hat Enterprise Linux AS release 3 (Taroon)
[EMAIL PROTECTED] regress]$ uname -a
Linux lora01 2.4.21-9.0.1.ELsmp #1 SMP Mon Feb 9 22:26:51 EST 2004 i686
i686 i386 GNU/Linux
Bruce Momjian
Thomas Hallgren [EMAIL PROTECTED] writes:
Perhaps you should either change this behavior or make a note it in
Writing Trigger Functions in C?
Okay, I've changed the text thusly:
diff -r1.35 trigger.sgml
434,435c434,437
A trigger function must return either symbolNULL/ or a
Tom Lane wrote:
Why not?
The real answer is it's historical and I didn't see any need to
change it. But one could argue that a function returning NULL
doesn't know it's supposed to be a trigger.
The reason I ask is that this behavior just bit me in PL/Java. Triggers
returning null didn't
Peter Eisentraut wrote:
There is also a big difference between supporting some proprietary
software and making proprietary software a de facto requirement for
participating in the development effort.
Just to complete the information on this, I have it on good authority
(i.e. from Larry
Is there a way to do that without too much (mwahahhaha! fiddling with
pg_class!!!) trickery?
esp=# alter table test add primary key(id);
NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index
test_pkey for table test
ALTER TABLE
---(end of
Gaetano Mendola wrote:
a1) If exist check that is a 16MB file ( the request can
~arrive during the copy ),
I think this will fail under windows: copy first sets the file size
and then transfers the data. I wouldn't rule out that some Unices use
the same implementation.
~
Am Freitag, 13. August 2004 15:18 schrieb Zoltan Bartko:
here goes the last missing bunch of strings translated to sk.
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 8: explain analyze is
Am Freitag, 13. August 2004 14:31 schrieb Zoltan Bartko:
attached you may find another bunch of translated strings.
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Don't 'kill -9' the
Am Freitag, 13. August 2004 06:39 schrieb Zoltan Bartko:
here's another bunch of message strings translated into sk_SK.
Installed.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: if posting/reading
Bruce Momjian [EMAIL PROTECTED] writes:
Someone on IRC just reported this to_char() failure with negative
intervals:
I think Karel wanted to remove to_char(interval) altogether.
regards, tom lane
---(end of broadcast)---
Manfred Spraul wrote:
Gaetano Mendola wrote:
a1) If exist check that is a 16MB file ( the request can
~arrive during the copy ),
I think this will fail under windows: copy first sets the file size
and then transfers the data. I wouldn't rule out that some Unices use
the
Chris Browne [EMAIL PROTECTED] writes:
I have a table that has a candidate primary key (e.g. - unique, not
null) that I wish to actually assert _is_ a primary key.
Is there a way to do that without too much (mwahahhaha! fiddling with
pg_class!!!) trickery?
Why don't you just ALTER TABLE ADD
[EMAIL PROTECTED] (Henry) writes:
As part of the project, we need to implement a new feature for the
trigger creation in
PostgreSQL, which defines aliases for the old and new data by
adding
the REFERENCING clause to the CREATE TRIGGER statement. Based on my
research, the following items
Daniel Schuchardt [EMAIL PROTECTED] writes:
i tried a bit with errorhandling and found the following :
(i want to ignore the dublicate key exception)
ERROR: SPI_prepare failed for ROLLBACK: SPI_ERROR_TRANSACTION
You can't use ROLLBACK inside a plpgsql function. I agree that this
error
Christopher Browne [EMAIL PROTECTED] writes:
Oops! [EMAIL PROTECTED] (Reinoud van Leeuwen) was seen spray-painting on a wall:
Why? I understood that using BitKeeper for free for Open Source projects
is allowed. (but IANAL).
Ah, but there's a problem with BK _actually seen in production_ in
Andreas Krennmair [EMAIL PROTECTED] writes:
creating template1 database in data/base/1 ... FATAL: XX000: failed to
initialize lc_monetary to C
LOCATION: InitializeGUCOptions, guc.c:2337
child process exited with exit code 1
As an important note you have to know that diet libc's support for
Kind people,
I've brought this up before, and with Dennis Bjőrklund's help, would
like to bring it up again. Here's the idea:
I'd like to be able to create functions with named parameters that
could be called with the names in any order. For example,
CREATE OR REPLACE FUNCTION foo_func(name
Gaetano Mendola [EMAIL PROTECTED] writes:
I'm facing however to the following problems:
1) Discovery the actual WAL file
I'm supposing is the last modified file inside the
pg_xlog directory. If this is not the good method
may I know how I can know it ?
While that
David Fetter [EMAIL PROTECTED] writes:
CREATE OR REPLACE FUNCTION foo_func(name TEXT, val INTEGER) AS ...
SELECT foo_func(val AS 23, name AS 'Name goes here');
I don't think that syntax will work. You could possibly do it the other
way round:
SELECT foo_func(23 AS val, 'Name goes here' AS
David Fetter wrote:
Dennis has pointed out that mixing the call-with-named-parameter
interface with call-by-order-of-parameters one would cause confusion,
and I think it would be OK to disallow this type mixing, so
SELECT foo_func(name AS 'yet another name', 35);
would be disallowed.
Python's
I would personally find this useful, but I would suggest using Oracle's
syntax of SELECT func(a=2, b='b', ...);
Having said that, having the concept of DEFAULT for parameters wolud be
even more useful, ie:
CREATE FUNCTION blah (
a int
, b int DEFAULT 0
);
SELECT blah(1,0);
and
SELECT
Tom Lane wrote:
Christopher Browne [EMAIL PROTECTED] writes:
Oops! [EMAIL PROTECTED] (Reinoud van Leeuwen) was seen spray-painting on a wall:
Why? I understood that using BitKeeper for free for Open Source projects
is allowed. (but IANAL).
Ah, but there's a problem with BK _actually
On Fri, Aug 13, 2004 at 06:22:25PM -0400, Tom Lane wrote:
On a related note, it would also be nice to have default
parameters and some way to say to use them.
That is fundamentally not ever going to happen, because it blows
overloaded-function resolution out of the water: there is no way
On Thu, Aug 12, 2004 at 01:13:46PM -0400, Tom Lane wrote:
Kenneth Marshall [EMAIL PROTECTED] writes:
On Thu, Aug 12, 2004 at 09:58:56AM -0400, Tom Lane wrote:
How would a read-only action work to block out the checkpoint?
The latch+version number is use by the checkpoint process. The
Andrew Dunstan [EMAIL PROTECTED] writes:
The attached patch appears to solve the problem. However, while it
makes us conform to the first sentence below from the docs, it doesn't
comply with the second. Not sure what to do about that. Maybe there's
a better solution?
Attached patch seems
Please could we have a development schedule page on the web site...?
The information it should contain would be like this (and others)
Current Development Release: (Coordinator: Bruce Momjian)
8.0:Beta1, released 2 August 2004
Beta2, deadline 2 September 2004
Jim C. Nasby [EMAIL PROTECTED] writes:
IOW, their function resolution code treats a(int, int default 0) as
being equivalent to a(int) and a(int, int).
So you are willing to prohibit a(int) from existing in parallel with
a(int, int-with-a-default) ?
I'll be interested to see the unique-index
Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
I'm facing however to the following problems:
1) Discovery the actual WAL file
I'm supposing is the last modified file inside the
pg_xlog directory. If this is not the good method
may I know how I can know it ?
Tom Lane wrote:
On a related note, it would also be nice to have default
parameters and some way to say to use them.
That is fundamentally not ever going to happen, because it blows
overloaded-function resolution out of the water: there is no way to
choose whether foo(42, 2.5) matches foo(int,
Gaetano Mendola wrote:
Oliver Jowett wrote:
David Fetter wrote:
Dennis has pointed out that mixing the call-with-named-parameter
interface with call-by-order-of-parameters one would cause confusion,
Python's equivalent syntax allows you to mix the two forms so long as
all the by-position
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Please could we have a development schedule page on the web site...?
You haven't been around here long, have you? There is no schedule.
The page would spend most of its time looking like
Current Development Release: (Coordinator: Bruce Momjian)
Oliver Jowett wrote:
David Fetter wrote:
Dennis has pointed out that mixing the call-with-named-parameter
interface with call-by-order-of-parameters one would cause confusion,
and I think it would be OK to disallow this type mixing, so
SELECT foo_func(name AS 'yet another name', 35);
would be
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
This is not a provably correct state machine
I think the discussion ends right there. You are assuming that the
commit is guaranteed to finish in X amount of time, when it is not
possible to make any such guarantee. We are not putting in an
Tom Lane
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Please could we have a development schedule page on the web site...?
You haven't been around here long, have you?
Gee, Tom, you noticed? What gave it away? :)
(I wasn't in a legal position to contribute before late 2003 - binding IP
Tom Lane
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
This is not a provably correct state machine
I think the discussion ends right there.
Yes...
Negative results are worth documenting too, IMHO.
Best Regards, Simon Riggs
---(end of
I notice that PITR doesn't function correctly on Windows. Has that been
reported elsewhere?
The archive_command parameter %p resolves to a full path containing slashes
rather than backslashes. This is not a Windows file, so any attempt to copy
it fails. There isn't any way to avoid that.
I'm
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
The attached patch appears to solve the problem. However, while it
makes us conform to the first sentence below from the docs, it doesn't
comply with the second. Not sure what to do about that. Maybe there's
a better solution?
[EMAIL PROTECTED] wrote:
I notice that PITR doesn't function correctly on Windows. Has that been
reported elsewhere?
The archive_command parameter %p resolves to a full path containing slashes
rather than backslashes. This is not a Windows file, so any attempt to copy
it fails. There isn't any
On Friday 13 August 2004 19:37, Tom Lane wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Please could we have a development schedule page on the web site...?
You haven't been around here long, have you? There is no schedule.
The page would spend most of its time looking like
Current
Would it be any better to allow
SELECT blah(1,DEFAULT);
?
Robert Treat
On Friday 13 August 2004 18:49, Jim C. Nasby wrote:
I would personally find this useful, but I would suggest using Oracle's
syntax of SELECT func(a=2, b='b', ...);
Having said that, having the concept of DEFAULT for
Pierre-Frédéric Caillaud wrote:
Is there also a possibility to tell Postgres : I don't care if I lose 30
seconds of transactions on this table if the power goes out, I just want
to be sure it's still ACID et al. compliant but you can fsync less often
and thus be faster (with a
Enrique Arizón wrote:
Now that CA has open sourced Ingres what future do
you guess to Postgresql and MySQL?
Don't missunderstand me, I have been using Postgresql
for more than 3 years and developing apps against it
and all I got is possitive impressions, but comparing
the upcoming 8.0
Robert Treat [EMAIL PROTECTED] writes:
Not sure how much more useful this is, but generally the first RC goes out
once all the open items are dealt with. Also doc freeze is generally
expected at RC1 time (though errors in the docs are still acceptable fixes
for subsequent RC's)
Actually
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
I see this: there is no PUBLISHED schedule, there probably is no AGREED
schedule, but everybody's working to some reasonable working assumptions
which mean that there is in fact an IMPLICIT schedule. (Whether or not that
changes over time)
Well, if
Andrew Dunstan [EMAIL PROTECTED] writes:
Should it be backported for the upcoming stable release(s)? Bruce and I
were discussing this earlier.
Probably a good idea, since we do support psql on Windows even in the
older releases.
My personal opinion is to back-port only as far as 7.4, but if
Robert Treat [EMAIL PROTECTED] writes:
Would it be any better to allow
SELECT blah(1,DEFAULT);
Not a lot. If there is more than one 2-parameter blah(), how do you
pick? The DEFAULT gives you no clue at all about the type of the
second parameter...
I think if we wanted to do something like
Andrew Dunstan wrote:
[EMAIL PROTECTED] wrote:
I notice that PITR doesn't function correctly on Windows. Has that been
reported elsewhere?
The archive_command parameter %p resolves to a full path containing slashes
rather than backslashes. This is not a Windows file, so any attempt to
Tom Lane said:
Andrew Dunstan [EMAIL PROTECTED] writes:
Should it be backported for the upcoming stable release(s)? Bruce and
I were discussing this earlier.
Probably a good idea, since we do support psql on Windows even in the
older releases.
My personal opinion is to back-port only as
Andrew Dunstan [EMAIL PROTECTED] writes:
No, I think 7.4 should do. 7.3 users will still have the dos2unix workaround
available. Are you going to do the 7.4 patch, or do you need me to? I
normally only keep a HEAD tree checked out. A quick look at the cvsweb diffs
suggests the patch should
On Wed, 2004-08-11 at 16:43, Tom Lane wrote:
Gaetano Mendola [EMAIL PROTECTED] writes:
Tom Lane wrote:
It should work; dunno if anyone has tried it yet.
I was thinking about it but I soon realized that actually is
impossible to do, postgres replay the log only if during the
start the
Eric Kerin [EMAIL PROTECTED] writes:
The issues I've seen are:
1. Knowing when the master has finished the file transfer transfer to
the backup.
The standard solution to this is you write to a temporary file name
(generated off your process PID, or some other convenient reasonably-
unique
69 matches
Mail list logo