hi all,
I try to use the file pg_type.h who containing, pre-defined type like
INT4IOD, INT2OID, INT8OID.
So I include in the file#include server/catalog/pg_type.h but I
have the followed error
C:\Program Files\PostgreSQL\8.3\include\server/catalog/pg_type.h(22) :
fatal error C1083: Cannot
I'm having a transaction problem when executing prepared statements using the
PHP PDO-PGSQL module.
What happens is this:
On the first $subItem, $checkSubscription goes well, but $insertReminderEntry
fails with error
Duplicate key violates unique constraint
This error should just be logged and
On Mon, Dec 01, 2008 at 10:14:52AM +0100, Bart Degryse wrote:
I'm having a transaction problem when executing prepared statements using the
PHP PDO-PGSQL module.
What happens is this:
On the first $subItem, $checkSubscription goes well, but $insertReminderEntry
fails with error
Duplicate
Siddharth Shah wrote:
I am compiling postgres, I have some doubts on ./configure options
--enable-nls[=LANGUAGES] enable Native Language Support
Do I need to supply each language name which i am going to store
in my database or just have to take support UTF-8 ?
You need to
Albe Laurenz wrote:
Siddharth Shah wrote:
I am compiling postgres, I have some doubts on ./configure options
--enable-nls[=LANGUAGES] enable Native Language Support
Do I need to supply each language name which i am going to store
in my database or just have to take
Siddharth Shah wrote:
I am compiling postgres, I have some doubts on ./configure options
--disable-largefile
Does it refers to for storing blob objects to store or
anything else ?
I couldn't find this configure switch in the documentation for
8.3 or 8.4. Can you explain where
Albe Laurenz wrote:
Siddharth Shah wrote:
I am compiling postgres, I have some doubts on ./configure options
--disable-largefile
Does it refers to for storing blob objects to store or
anything else ?
I couldn't find this configure switch in the documentation for
8.3 or
Albe Laurenz wrote:
Siddharth Shah wrote:
I am compiling postgres, I have some doubts on ./configure options
--disable-largefile
Does it refers to for storing blob objects to store or
anything else ?
I couldn't find this configure switch in the documentation for
8.3 or 8.4. Can
Thanks Martijn!
Martijn van Oosterhout [EMAIL PROTECTED] 2008-12-01 10:54
On Mon, Dec 01, 2008 at 10:14:52AM +0100, Bart Degryse wrote:
I'm having a transaction problem when executing prepared statements using the
PHP PDO-PGSQL module.
What happens is this:
On the first $subItem,
Siddharth Shah wrote:
In My Application I have only 256MB storage device and I have to
manage many other application in same storage
So, have to remove use less files , From configuration disabling
unwanted options helps to reduce the size.
So, I need detail description on compile
Albe Laurenz wrote:
Siddharth Shah wrote:
In My Application I have only 256MB storage device and I have to
manage many other application in same storage
So, have to remove use less files , From configuration disabling
unwanted options helps to reduce the size.
So, I need detail
2008/12/1 elekis [EMAIL PROTECTED]
hi all,
I try to use the file pg_type.h who containing, pre-defined type like
INT4IOD, INT2OID, INT8OID.
So I include in the file#include server/catalog/pg_type.h but I
have the followed error
C:\Program
Scott,
OK, find out how to create users on your gentoo server, and see if you
can figure out what's broken in emerge so you can install lftp. It's
much better than regular ftp, as it has assured transfer completion
and other useful features if you're interested in making sure the file
gets
Siddharth Shah wrote:
In My Application I have only 256MB storage device and I have to
manage many other application in same storage
Do you only need the PostgreSQL client or also the server?
Will that small storage device also contain the database?
Yes, I need to run Client Server both
When i read about 8.3 support indexed queries on NULL values (like rubric_id is
NULL) i was really happy.
But reality strike again... look like NULL in WHERE don't allow effective using
index on (rubric_id, pos) for queries like:
... WHERE rubric_id IS NULL ORDER BY pos LIMIT 5
Here is some
Reid,
since he noted the distro is '3 years old', odds are the portage tree is
out of date.
you can try a
sudo emerge --sync
and then
sudo emerge --ask lftp
note that if a sync has not been done in a long time, many packages may be
out of date ( possibly why the 'get' of left failed ).
elekis [EMAIL PROTECTED] writes:
I tried , in the command line to put
-I$(PGSQL_HOME)\include -I(PGSQL_HOME)\include\server
but, nothing change.
If that's really what you put, then you forgot a dollar sign...
regards, tom lane
--
Sent via pgsql-general mailing list
Martijn van Oosterhout wrote:
On Mon, Dec 01, 2008 at 10:14:52AM +0100, Bart Degryse wrote:
I'm having a transaction problem when executing prepared statements using the
PHP PDO-PGSQL module.
What happens is this:
On the first $subItem, $checkSubscription goes well, but $insertReminderEntry
Magnus Hagander [EMAIL PROTECTED] writes:
Albe Laurenz wrote:
My recommendation is to leave this switch alone and use the default;
you should not encounter any problems.
Agreed - the cost for supporting it is zero, AFAIK, so there is no
reason to turn it off unless the OS has a buggy
Siddharth Shah [EMAIL PROTECTED] writes:
In My Application I have only 256MB storage device and I have to
manage many other application in same storage
Quite honestly, you're going to need some other database besides
Postgres if you need a disk footprint that's only a fraction of 256MB.
Tom Lane wrote:
Siddharth Shah [EMAIL PROTECTED] writes:
In My Application I have only 256MB storage device and I have to
manage many other application in same storage
Quite honestly, you're going to need some other database besides
Postgres if you need a disk footprint that's
Maxim Boguk [EMAIL PROTECTED] writes:
Looks like when indexed search over NULL's added, planner wasn't learned
right way use such index on where something is NULL order by ... limit ...
queries.
There's nothing wrong with the plan; you've just got too many NULLs to
make it worth using the
hi all,
I tried your both solutions (and effectively, I forget the $ signe,
sorry) but know , I have that
C:\Program Files\PostgreSQL\8.3\include\server\nodes/nodes.h(390) :
error C2054: expected '(' to follow 'PGDLLIMPORT'
C:\Program Files\PostgreSQL\8.3\include\server\nodes/nodes.h(390) :
On Mon, Dec 1, 2008 at 12:10 AM, Owen Hartnett [EMAIL PROTECTED] wrote:
At 1:26 PM -0500 11/30/08, Tom Lane wrote:
Owen Hartnett [EMAIL PROTECTED] writes:
Yes, it did. I'm confused. My first parameter is a string, but the
following two are integers. I thought the paramType parameter
elekis [EMAIL PROTECTED] writes:
and my include is
#include catalog/pg_type.h
#include nodes/nodes.h
You need postgres.h first.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
Hi list,
First steps in trigger functions and PL/pgSQL so please bear with me...
How can one detect changes to certain fields in before update trigger
functions?
IF (NEW.column-name != OLD.column-name) THEN ...
doesn't work, so obviously my understanding of the values of the
varriables NEW
On Sunday 30 November 2008 11:18:12 pm Stéphane A. Schildknecht wrote:
Snip
Adrian Klaver a écrit :
When I run this test case I get:
test=# 2nd step : Deletion of command 1
test=# delete from commande where id=1;
ERROR: update or delete on table commande violates
On Monday 01 December 2008 7:27:48 am Adrian Klaver wrote:
On Sunday 30 November 2008 11:18:12 pm Stéphane A. Schildknecht wrote:
Snip
Adrian Klaver a écrit :
When I run this test case I get:
test=# 2nd step : Deletion of command 1
test=# delete from commande where id=1;
On Monday 01 December 2008 7:18:51 am Sebastian Tennant wrote:
Hi list,
First steps in trigger functions and PL/pgSQL so please bear with me...
How can one detect changes to certain fields in before update trigger
functions?
IF (NEW.column-name != OLD.column-name) THEN ...
doesn't work,
On Mon, Dec 1, 2008 at 7:18 AM, Sebastian Tennant
[EMAIL PROTECTED] wrote:
IF (NEW.column-name != OLD.column-name) THEN ...
The != operator doesn't work the way you might think when nulls are
thrown into the mix. I asked a similar question a while back and was
kindly pointed to the following
Hello.
I am looking for a Chinese dictionary for TSearch2 Postgresql feature,
with no success yet.
I found a reference on a chinese webpage:
http://code.google.com/p/nlpbamboo/wiki/TSearch2
With the help of translate.google.com, I thought managed to figure out
what to do: I installed
Quoth Adrian Klaver [EMAIL PROTECTED]:
On Monday 01 December 2008 7:18:51 am Sebastian Tennant wrote:
I had thought that OLD holds the record as it was before the update,
and that NEW holds the record as it is since the update (but before
the update has been committed)?
'42.10 Trigger
Quoth Richard Broersma [EMAIL PROTECTED]:
On Mon, Dec 1, 2008 at 7:18 AM, Sebastian Tennant
[EMAIL PROTECTED] wrote:
IF (NEW.column-name != OLD.column-name) THEN ...
The != operator doesn't work the way you might think when nulls are
thrown into the mix. I asked a similar question a
sudo emerge --sync
...
deleting xfce-extra/xfce4-weather/files/digest-xfce4-weather-0.4.9
deleting xfce-extra/xfce4-weather/files/digest-xfce4-weather-0.4.1
deleting xfce-extra/xfce4-weather/files/digest-xfce4-weather-0.4.0
deleting
On Mon, Dec 1, 2008 at 8:35 AM, Sebastian Tennant
[EMAIL PROTECTED] wrote:
IF (NEW.column-name != OLD.column-name) THEN ...
IF( NEW.* IS DISTINCT FROM OLD.* ) THEN ...
I sometimes think this kind of gotcha is purposely buried, or not
addressed at all, in order to force users to read the
Sebastian Tennant [EMAIL PROTECTED] writes:
I sometimes think this kind of gotcha is purposely buried, or not
addressed at all, in order to force users to read the manual.
Where exactly do you think we should document it, if not in the manual?
In any case it's SQL-standard behavior that any
If my perusal of the sql generated by pg_dump is correct, then it
doesn't appear that it's wrapped in a transaction, and thus might be
able to only complete a partial restore?
Or does
psql myDatabase mypg_dumpfile
wrap the file stream in a transaction?
If not, is there a reason why it
Owen Hartnett [EMAIL PROTECTED] writes:
If my perusal of the sql generated by pg_dump is correct, then it
doesn't appear that it's wrapped in a transaction, and thus might be
able to only complete a partial restore?
That's correct, and intentional. You can use pg_restore's -1 switch
or add
Owen Hartnett wrote:
If my perusal of the sql generated by pg_dump is correct, then it
doesn't appear that it's wrapped in a transaction, and thus might be
able to only complete a partial restore?
You're right, it is not. Try pg_restore --single-transaction. (You'll
need pg_dump -Fc
Quoting Owen Hartnett [EMAIL PROTECTED]:
If my perusal of the sql generated by pg_dump is correct, then it
doesn't appear that it's wrapped in a transaction, and thus might be
able to only complete a partial restore?
Or does
psql myDatabase mypg_dumpfile
Try to use pg_restore with the
At 12:37 PM -0500 12/1/08, Tom Lane wrote:
Owen Hartnett [EMAIL PROTECTED] writes:
If my perusal of the sql generated by pg_dump is correct, then it
doesn't appear that it's wrapped in a transaction, and thus might be
able to only complete a partial restore?
That's correct, and
Quoth Richard Broersma [EMAIL PROTECTED]:
On Mon, Dec 1, 2008 at 8:35 AM, Sebastian Tennant
[EMAIL PROTECTED] wrote:
IF (NEW.column-name != OLD.column-name) THEN ...
IF( NEW.* IS DISTINCT FROM OLD.* ) THEN ...
I sometimes think this kind of gotcha is purposely buried, or not
addressed at
On Mon, Dec 1, 2008 at 12:04, Andrus [EMAIL PROTECTED] wrote:
sudo emerge --sync
* An update to portage is available. It is _highly_ recommended
* that you update portage now, before any other packages are updated.
* Please run 'emerge portage' and then update ALL of your
* configuration
your /usr/portage directory is probably not mounted properly check that
again and then check /etc/make.profile points to a valid directory which
will be something along the lines of
/usr/portage/profiles/default-linux/arch/version
jomanda etc # ls /etc/make.profile -l
lrwxrwxrwx 1 root root
Quoth Tom Lane [EMAIL PROTECTED]:
Sebastian Tennant [EMAIL PROTECTED] writes:
I sometimes think this kind of gotcha is purposely buried, or not
addressed at all, in order to force users to read the manual.
Where exactly do you think we should document it, if not in the
manual?
I clearly
as previously said you need to go to http://forums.gentoo.org/
On Mon, Dec 1, 2008 at 13:16, Andrus [EMAIL PROTECTED] wrote:
your /usr/portage directory is probably not mounted properly check that
again and then check /etc/make.profile points to a valid directory which
will be something along
Adrian Klaver [EMAIL PROTECTED] writes:
The problem as far as I can tell is tuple visibility.
Sort of: the triggers on commandeligne fire (and update the commande row)
at completion of the DELETE command inside p_commande_bd. This means
that by the time control returns from that trigger, the
Sebastian Tennant wrote:
P.S. Emacs users of PostgreSQL might like to know that there's a
texinfo version of the manual (version 8.3.3) available for
download from here:
http://www.emacswiki.org/PostGreSQL
Hmm, we did have a patch to add a texinfo target to the docs
http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html
All interesting, but especially the part about half-way down under the
heading So what went wrong with MySQL 5.1 ? - must-read for anyone
involved in selecting a database.
Cheers,
Steve
--
Sent via
On Mon, Dec 1, 2008 at 8:00 PM, Steve Crawford
[EMAIL PROTECTED] wrote:
http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html
All interesting, but especially the part about half-way down under the
heading So what went wrong with MySQL 5.1 ? - must-read for
On Mon, Dec 1, 2008 at 1:05 PM, Grzegorz Jaśkiewicz [EMAIL PROTECTED] wrote:
On Mon, Dec 1, 2008 at 8:00 PM, Steve Crawford
[EMAIL PROTECTED] wrote:
http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html
All interesting, but especially the part about half-way
On Mon, 2008-12-01 at 20:05 +, Grzegorz Jaśkiewicz wrote:
On Mon, Dec 1, 2008 at 8:00 PM, Steve Crawford
[EMAIL PROTECTED] wrote:
http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html
All interesting, but especially the part
2008/12/1 Scott Marlowe [EMAIL PROTECTED]:
I'd rather do the paritioning by hand and use slony and know it works
than rely on the code that's doing all that in mysql. If your server
crashes while updating a partitioned table, you could lose all the
data in it. Replication can mysteriously
- Tom Lane [EMAIL PROTECTED] wrote:
Adrian Klaver [EMAIL PROTECTED] writes:
The problem as far as I can tell is tuple visibility.
Sort of: the triggers on commandeligne fire (and update the commande
row)
at completion of the DELETE command inside p_commande_bd. This means
that by
On Mon, Dec 01, 2008 at 08:05:48PM +, Grzegorz Jaśkiewicz wrote:
well, at least they have replication and partitioning built in.
That will provide excellent comfort to the users.
HaplessUser: Your replication crashed and took all of my slaves with
it, and then my primary database crashed
Sorry with all my respect to you, you look like wrong.
Here example:
With NULL's:
mboguk_billing=# EXPLAIN ANALYZE SELECT * from cluster_weight where
cluster_weight.rubric_id IS NULL ORDER BY pos LIMIT 5;
QUERY PLAN
Maxim Boguk wrote:
Sorry with all my respect to you, you look like wrong.
The difference is that the plan with -1 does not need to sort the
output, because it comes sorted out of the index; so the execution can
be stopped as soon as 5 tuples have come out. With NULL, that can't be
done.
--
Adrian Klaver [EMAIL PROTECTED] writes:
Thanks for the explanation. Just so I am clear,the act of updating the row in
p_commandeligne_ad creates a new tuple for the row with id of 1. This means
the original statement delete from commande where id=1 runs against a
version of the row that no
Grzegorz Jaśkiewicz wrote:
On Mon, Dec 1, 2008 at 8:00 PM, Steve Crawford
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html
All interesting, but especially the part about half-way down under
Alvaro Herrera wrote:
Maxim Boguk wrote:
Sorry with all my respect to you, you look like wrong.
The difference is that the plan with -1 does not need to sort the
output, because it comes sorted out of the index; so the execution can
be stopped as soon as 5 tuples have come out. With NULL,
Scara Maccai [EMAIL PROTECTED] writes:
I ran ANALYZE on both tables, but the plan shows rows=1 in the inner
table results.
If I change the left outer join into an inner join the bitmap index
scan of the inner table of the nested loop shows a correct number of
rows (not the exact same
Maxim Boguk [EMAIL PROTECTED] writes:
But why? NULL's have some special representation in index which don't work
same as normal values?
In general, NULLs don't work the same as normal values, no.
The reason this particular query isn't working as you are expecting is
that foo IS NULL isn't
I wonder if I'm the only one who just saved a copy of that post for
reference in case it gets forcibly removed...
Recently I was thinking about whether I had enough material to warrant a
2008 update to Why PostgreSQL instead of MySQL; who would have guessed
that Monty would do most of the
Geoffrey wrote:
Grzegorz Jaśkiewicz wrote:
On Mon, Dec 1, 2008 at 8:00 PM, Steve Crawford
[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
http://monty-says.blogspot.com/2008/11/oops-we-did-it-again-mysql-51-released.html
All interesting, but especially the part about
On 01/12/2008 18:39, Vignesh Raaj wrote:
Can anyone please help in getting a solution...
Cross-posting to lots of inappropriate lists is not going to endear you
to many people, and is going to decrease, not increase, your chance of
getting an answer.
You should post to -general only with this
Greg Smith wrote:
I wonder if I'm the only one who just saved a copy of that post for
reference in case it gets forcibly removed...
Recently I was thinking about whether I had enough material to warrant
a 2008 update to Why PostgreSQL instead of MySQL; who would have
guessed that Monty would
On Mon, Dec 1, 2008 at 4:10 PM, Jason Long
[EMAIL PROTECTED] wrote:
Greg Smith wrote:
I wonder if I'm the only one who just saved a copy of that post for
reference in case it gets forcibly removed...
Recently I was thinking about whether I had enough material to warrant a
2008 update to Why
Scott Marlowe wrote:
On Mon, Dec 1, 2008 at 4:10 PM, Jason Long
[EMAIL PROTECTED] wrote:
Greg Smith wrote:
I wonder if I'm the only one who just saved a copy of that post for
reference in case it gets forcibly removed...
Recently I was thinking about whether I had enough material to
Stephane Bortzmeyer wrote:
On Thu, Nov 27, 2008 at 02:34:17AM +0900,
Craig Ringer [EMAIL PROTECTED] wrote
a message of 188 lines which said:
ERROR: character 0xc3bd of encoding UTF8 has no equivalent in WIN1251
Which it does not; that character is ??? (HANGUL SYLLABLE SSYEG)
No, I
The transaction where COMMIT PREPARED was slow basically did the
following 20 times:
- create a child table T1 as select from another child table T2
- drops child table T2
- renames T1 to T2
What here would cause the 2PC state file to grow large? In my rough
experiments, its size seems
John Smith [EMAIL PROTECTED] writes:
The transaction where COMMIT PREPARED was slow basically did the
following 20 times:
- create a child table T1 as select from another child table T2
- drops child table T2
- renames T1 to T2
What here would cause the 2PC state file to grow large? In
On Mon, Dec 1, 2008 at 8:43 PM, Geoffrey [EMAIL PROTECTED]wrote:
Grzegorz Jaśkiewicz wrote:
well, at least they have replication and partitioning built in. How
reliable it is, is completely another story - but still, they are a step
ahead in that regard. Now I know why Tom Lane doesn't have
On Mon, Dec 1, 2008 at 7:49 PM, Grzegorz Jaśkiewicz [EMAIL PROTECTED] wrote:
which reminds me, of my favourite recent quote:
Think I'll go fix this while I'm watching the football game ...
We really need a favorite Tom Lane quotes thread. Mine is (roughly):
We don't support that, but you're
=?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= [EMAIL PROTECTED] writes:
which reminds me, of my favourite recent quote:
Think I'll go fix this while I'm watching the football game ...
Well, the Steelers were up 23-10 at that point, so the game no longer
demanded too much attention ...
Scott Marlowe [EMAIL PROTECTED] writes:
We really need a favorite Tom Lane quotes thread. Mine is (roughly):
We don't support that, but you're free to try it, you just get to keep
both pieces if it breaks.
Hate to disillusion you, but that's a standard comment around Red Hat.
I have no idea
Tom Lane wrote:
Scott Marlowe [EMAIL PROTECTED] writes:
We really need a favorite Tom Lane quotes thread. Mine is (roughly):
We don't support that, but you're free to try it, you just get to keep
both pieces if it breaks.
Hate to disillusion you, but that's a standard
Quoth Alvaro Herrera [EMAIL PROTECTED]:
Sebastian Tennant wrote:
P.S. Emacs users of PostgreSQL might like to know that there's a
texinfo version of the manual (version 8.3.3) available for
download from here:
http://www.emacswiki.org/PostGreSQL
Hmm, we did have a
On Wed, Nov 26, 2008 at 3:36 PM, Karina Guardado [EMAIL PROTECTED] wrote:
I have a problem I have created a database with encoding SQL_ASCII and when
I insert the data using a terminal in linux and insert the data for example
Insert into mytable values(1,'Eléctrico'); it works fine but if I try
Tom on things that might ruin his tape backups:
Then of course there are the *other* risks, such as the place burning to
the ground, or getting drowned by a break in the city reservoir that's a
couple hundred yards up the hill...Or maybe being burgled by Oracle
employees who are specifically
On Tue, 2008-12-02 at 00:37 -0500, Greg Smith wrote:
Tom on things that might ruin his tape backups:
Then of course there are the *other* risks, such as the place burning to
the ground, or getting drowned by a break in the city reservoir that's a
couple hundred yards up the hill...Or maybe
On Mon, Dec 1, 2008 at 10:42 PM, Joshua D. Drake [EMAIL PROTECTED] wrote:
On Tue, 2008-12-02 at 00:37 -0500, Greg Smith wrote:
Tom on things that might ruin his tape backups:
Then of course there are the *other* risks, such as the place burning to
the ground, or getting drowned by a break in
On Tue, Dec 2, 2008 at 5:44 AM, Scott Marlowe [EMAIL PROTECTED]wrote:
Apparently something to do with backups. But I don't know what those
are either... :-P
well, we're all waiting for built in replication ;)
About the tapes, I love that Oracle emps bit :D
Sure, they write too much java
Scott Marlowe wrote:
On Mon, Dec 1, 2008 at 10:42 PM, Joshua D. Drake [EMAIL PROTECTED] wrote:
On Tue, 2008-12-02 at 00:37 -0500, Greg Smith wrote:
Tom on things that might ruin his tape backups:
Then of course there are the *other* risks, such as the place burning to
the ground, or getting
Hi,
I need to know how I can easily get data for just one table from postgres
dump database backup.
Kind regards,
P.
Hi guys,
What happened to pgadmin3 rpms for fedora core 10?
Aren't they built yet?
BR,
Pedro Doria Meunier
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
am Tue, dem 02.12.2008, um 10:21:51 +0300 mailte Otandeka Simon Peter
folgendes:
Hi,
I need to know how I can easily get data for just one table from postgres dump
database backup.
Binary dump for pg_restore? If so, you can use the -L - Option.
ASCII-Dump: If so, edit the file.
Andreas
#include postgres.h
#include catalog/pg_type.h
#include nodes/nodes.h
heu... I have that now
rcqpgsql.c
c:\program files\postgresql\8.3\include\server\pg_config.h(116) :
warning C4005: 'HAVE_FINITE' : macro redefinition
C:\Program Files\MySQL\MySQL Server
5.0\include\config-win.h(286)
87 matches
Mail list logo
