Gregory Youngblood <[EMAIL PROTECTED]> writes:
> On Jul 27, 2005, at 9:53 PM, Tom Lane wrote:
>> You'd have to translate that to NUMERIC, which would work but would
>> take a bit of a performance hit ...
> The most common places I've seen unsigned bigint used have been
> primary keys for tables
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Wed, Jul 27, 2005 at 05:13:01PM -0700, Chris Travers wrote:
>> Thomas F. O'Connell wrote:
>>> I'm not sure why you're getting errors. Is there a reason you did the
>>> schema dump separately from the data dump rather than a monolithic
>>> dump/res
On Jul 27, 2005, at 9:53 PM, Tom Lane wrote:Gregory Youngblood <[EMAIL PROTECTED]> writes: ... the problem is unsigned bigint in mysql to postgresql. There's not another larger integer size that can be used that would allow the 18446744073709551615 (is that the max value?) max value available in
Gregory Youngblood <[EMAIL PROTECTED]> writes:
> ... the problem is unsigned bigint in mysql to postgresql.
> There's not another larger integer size that can be used that would
> allow the 18446744073709551615 (is that the max value?) max value
> available in mysql. Or am I missing something
Christopher Kings-Lynne wrote:
So far, the checklist I can see includes:
* Maintaining conversion scripts
What I think we need is a C program that dumps directly from MySQL
into PostgreSQL sql.
ie. Take the mysqldump source code and just modify its output.
Will inherit the MySQL license
Also sprach Scott Marlowe ([EMAIL PROTECTED])
> On Wed, 2005-07-27 at 15:57, John DeSoi wrote:
> > On Jul 27, 2005, at 4:46 PM, Scott Marlowe wrote:
> >
> > > So, how can two databases, not currently talking to one another,
> > > guarantee that their GUIDs don't collide? using a large randomly
> >
I don't think it would be that slow, unless running on a modem.
It would really depend on what you are doing, calling dblink 1000 times
a second would be slow, but I could see it being
used succesfully for other applications.
Alvaro Herrera wrote:
On Wed, Jul 27, 2005 at 05:40:11PM -0500, Ton
Josh Berkus wrote:
KL-
What I think we need is a C program that dumps directly from MySQL into
PostgreSQL sql.
Why C? PerlDBI or JDBC should be able to do this readily enough.
Uhmmm isn't that what fetters DBI-Link thing does?
--
Your PostgreSQL solutions provider, Command Prompt, In
I think one of the more difficult areas will be to convert unsigned
fields from mysql into postgres. For smaller sizes it is possible to
convert to postgres by moving one size up and using constraints to
restrict numbers to be positive, and possibly within the mysql range
too. But, the prob
If linking it in directly via C would bring in the MySQL license, and
you want to avoid that, what about one of the scripting languages
such as perl or python, or possibly even ruby? Or, what about using
UnixODBC to talk to MySQL.
I've written a few perl scripts when I need to convert MySQL
On Jul 28, 2005, at 11:20 AM, Christopher Kings-Lynne wrote:
What I think we need is a C program that dumps directly from MySQL
into PostgreSQL sql.
ie. Take the mysqldump source code and just modify its output.
Will inherit the MySQL license though :(
Just the conversion program would, c
KL-
> What I think we need is a C program that dumps directly from MySQL into
> PostgreSQL sql.
Why C? PerlDBI or JDBC should be able to do this readily enough.
--
Josh Berkus
Aglio Database Solutions
San Francisco
---(end of broadcast)---
TIP
So far, the checklist I can see includes:
* Maintaining conversion scripts
What I think we need is a C program that dumps directly from MySQL into
PostgreSQL sql.
ie. Take the mysqldump source code and just modify its output.
Will inherit the MySQL license though :(
Chris
---
Jaime Casanova <[EMAIL PROTECTED]> writes:
> On 7/26/05, Csaba Nagy <[EMAIL PROTECTED]> wrote:
>> Seq Scan on big_table (cost=0.00..2447201.85 rows=448 width=16)
>> Filter: ((bigint_col_2 = 12132131::bigint) OR NULL::boolean)
>>
>> Considering that NULL::boolean is always false,
> null::boolean
Interesting, How would I specify the order of the tables on the commandline
To Thomas: I decided to separate the schema/data export/import to make sure the
schema was at least being created correctly...
How can I export one table by itself? Not just table, but a view/trigger,
etc... Is
it eve
On Wed, Jul 27, 2005 at 05:12:46PM -0700, Dr NoName wrote:
> Thanks a lot, everyone! That solved my problem. But I
> still want to be able to set transaction timeout. Any
> chance of that in the next release?
No, because feature freeze for the next release is one month past
already.
Anyway, I thi
On Wed, Jul 27, 2005 at 05:13:01PM -0700, Chris Travers wrote:
> Thomas F. O'Connell wrote:
>
> >The implicit indexes are no big deal; they're just a sign of indexes
> >getting created by PRIMARY KEYs on your tables.
> >
> >I'm not sure why you're getting errors. Is there a reason you did the
On Wed, Jul 27, 2005 at 07:43:08PM -0400, John DeSoi wrote:
> I'm not saying that GUIDs are the ultimate solution to this problem.
> The original poster brought up the need to store GUIDs in a database.
> There are protocols and standards that require GUIDs and I merely
> agree it would be n
Dr NoName wrote:
Sure. Like this:
Client A accesses table T, and "hangs."
Client B attempts to get an ACCESS EXCLUSIVE lock on
table T in
preparation for VACUUM FULL.
Client C connects to the database and waits for
client B to get and
release his lock on table T.
Client D connects to the datab
Thanks a lot, everyone! That solved my problem. But I
still want to be able to set transaction timeout. Any
chance of that in the next release?
Eugene
--- Scott Marlowe <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-07-27 at 10:31, Dr NoName wrote:
> > > Sure. Like this:
> > >
> > > Client A acces
Thomas F. O'Connell wrote:
Jonathan,
The implicit indexes are no big deal; they're just a sign of indexes
getting created by PRIMARY KEYs on your tables.
I'm not sure why you're getting errors. Is there a reason you did the
schema dump separately from the data dump rather than a monolit
On Jul 27, 2005, at 5:00 PM, Scott Marlowe wrote:
Then I would think a better thought out solution would be one where
your
unique ids ARE guaranteed to be unique, where you used something like
select 'astringuniqtothismachine'||nextval('localsequence');
That really would be guaranteed uniqu
On Wed, Jul 27, 2005 at 05:40:11PM -0500, Tony Caduto wrote:
> Use Dblink and do a select off of a sequence on just one of the boxes?
> You could set up a view that uses DBlink on all the boxes that points to
> the master seq box.
>
> should work.
It'll make the whole thing painfully slow.
--
On Wed, Jul 27, 2005 at 01:55:51PM -0400, Robert Treat wrote:
> On Wednesday 27 July 2005 12:30, Alvaro Herrera wrote:
> > On Wed, Jul 27, 2005 at 11:46:05AM -0400, Robert Treat wrote:
> > > Seems unlikely unless folks like Tom Lane, Stephan Szabo, and Richard
> > > Huxton have unsubscribed and res
Use Dblink and do a select off of a sequence on just one of the boxes?
You could set up a view that uses DBlink on all the boxes that points to
the master seq box.
should work.
Scott Marlowe wrote:
So, how can two databases, not currently talking to one another,
guarantee that their GUIDs do
On Jul 27, 2005, at 3:43 PM, Jonathan Villa wrote:
My approach will be/has been as follows:
I've used pg_dump of 7.4 to do
pgsql-7.4 $>pg_dump --schema-only dbName > schema.sql
Aside from some tweaking, the import seemed to work fine.
Now, I'm attempting the following
pgsql-7.4 $> pg_dump
Am Mittwoch, den 27.07.2005, 23:03 +0200 schrieb Magnus Hagander:
> > > This is not really a viable replacement for a GUID ==
> > globally unique
> > > identifier. Here global means that if I use the application in
> > > multiple databases, I'm guaranteed that no two identifiers
> > will be the
There is a "privacy hole" from using the MAC address. (Read it in the
WIKI article someone else posted).
Probably, it would be better to use a one way hash of the MAC address.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf Of Chris Tr
Magnus Hagander wrote:
At least on Windows, the GUID is derived in part from the computers
primary MAC address. No, it's not a guarantee, but it's pretty unlikely
:-)
The danger is not that the MAC address will be duplicated, but that
other factors will lead to an MD5 collision.
Unless
You could guarantee it, for example...
Something like (pseudocode here):
create sequence local_id;
create domain guid AS text default ('54-' || (nextval(local_id))::text);
where 54 is the database id. In this way, every inserted GUID will be
guaranteed to contain a GUID in two parts: A databas
On Wed, 2005-07-27 at 15:57, John DeSoi wrote:
> On Jul 27, 2005, at 4:46 PM, Scott Marlowe wrote:
>
> > So, how can two databases, not currently talking to one another,
> > guarantee that their GUIDs don't collide? using a large randomly
> > generated name space only reduces the chances of collis
On Jul 27, 2005, at 4:46 PM, Scott Marlowe wrote:
So, how can two databases, not currently talking to one another,
guarantee that their GUIDs don't collide? using a large randomly
generated name space only reduces the chances of collision, it doesn't
actually guarantee it.
Like MD5, there is
> > This is not really a viable replacement for a GUID ==
> globally unique
> > identifier. Here global means that if I use the application in
> > multiple databases, I'm guaranteed that no two identifiers
> will be the
> > same. Using a sequence will only support uniqueness for a single
> >
Windows uses the MAC address in GUID generation.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:pgsql-general-
> [EMAIL PROTECTED] On Behalf Of Scott Marlowe
> Sent: Wednesday, July 27, 2005 1:47 PM
> To: John DeSoi
> Cc: Tino Wildenhain; Riaan van der Westhuizen; Postgresql-Genera
Yes, this is the problem with GUIDs... you can calculate them by mashing
toghether things like the time, a network address, and some random
numbers, which makes it very unlikely for a collision but at the end
of the day that G stand for global, *not* guaranteed.
On Wed, 27 Jul 2005, Scott Marl
On Wed, 2005-07-27 at 15:32, John DeSoi wrote:
> On Jul 27, 2005, at 4:49 AM, Tino Wildenhain wrote:
>
> > I'd create a sequence:
> >
> > CREATE SEQUENCE global_unique_id_seq;
> >
> > and a function:
> >
> > CREATE OR REPLACE FUNCTION newid()
> > RETURNS text AS
> > $BODY$ SELECT nextval('global
On Jul 27, 2005, at 4:49 AM, Tino Wildenhain wrote:
I'd create a sequence:
CREATE SEQUENCE global_unique_id_seq;
and a function:
CREATE OR REPLACE FUNCTION newid()
RETURNS text AS
$BODY$ SELECT nextval('global_unique_id_seq')::text; $BODY$
LANGUAGE 'sql' VOLATILE;
now every call to new
On 7/27/05, Stephan Szabo <[EMAIL PROTECTED]> wrote:
>
> I think the where t2.column_id is null where column_id is the joining
> column makes this a form of not exists, so maybe:
>
> DELETE FROM t1 WHERE NOT EXISTS (SELECT 1 FROM t2 WHERE t2.column_id =
> t1.columnid);
>
>
This looks good. Tha
On 7/26/05, Csaba Nagy <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Jumping in directly to the subject, this is what I get:
>
> explain SELECT bigint_col_1, bigint_col_2 FROM big_table WHERE
> bigint_col_2 in (12132131, null, null, null,
> null);
>
> QUERY PLAN
>
My approach will be/has been as follows:
I've used pg_dump of 7.4 to do
pgsql-7.4 $>pg_dump --schema-only dbName > schema.sql
Aside from some tweaking, the import seemed to work fine.
Now, I'm attempting the following
pgsql-7.4 $> pg_dump --data-only --inserts dbName > data.sql
and when I a
On Wed, 27 Jul 2005, Brian Wong wrote:
> I am currently migrating from MySQL to PostgreSQL and I have found
> that some queries do not work. For instance,
>
> DELETE t1 FROM t1 LEFT JOIN t2 USING (column_id) WHERE t2.column_id IS NULL;
>
> works in MySQL. This works as expected even though the MyS
So, it seems to me that there is a fair bit of work to be done on
helping people migrate MySQL to PostgreSQL.
So far, the checklist I can see includes:
* Maintaining conversion scripts
* Reviewing pain points and looking at ways of mitigating them.
* Building solid migration documentation
*
I'm trying to port an extension that previously ran under Postgres on
linux so that it runs under PostgreSQL 8.0.3 on Windows. I'm using MingGW
for the compiling/linking.
I'm getting problems when I try to link though. Symbols that are defined
in the Postgres server and referenced in my extension
On Wed, Jul 27, 2005 at 15:28:36 -0400,
Brian Wong <[EMAIL PROTECTED]> wrote:
> I am currently migrating from MySQL to PostgreSQL and I have found
> that some queries do not work. For instance,
>
> DELETE t1 FROM t1 LEFT JOIN t2 USING (column_id) WHERE t2.column_id IS NULL;
>
> works in MySQL.
I am currently migrating from MySQL to PostgreSQL and I have found
that some queries do not work. For instance,
DELETE t1 FROM t1 LEFT JOIN t2 USING (column_id) WHERE t2.column_id IS NULL;
works in MySQL. This works as expected even though the MySQL
documentation does not mention the option of ha
Jonathan Villa wrote:
I've been googling a little bit and appears that 7.1 pretty old.
What steps are advised to upgrade from 7.1 to 7.4?
1. Dump the old db using 7.4's pg_dump.
2. Read the release notes for the in-between versions to make sure
nothing will impact your behaviour. Keep a close
On Wednesday 27 July 2005 11:41 am, Jonathan Villa wrote:
> I've been googling a little bit and appears that 7.1 pretty old.
Very.
> What steps are advised to upgrade from 7.1 to 7.4?
Unless there is some reason you really need 7.4, just go straight to
8.0.3.
Instructions start on page 230 of
On Wed, 2005-07-27 at 13:41, Jonathan Villa wrote:
> I've been googling a little bit and appears that 7.1 pretty old. What steps
> are
> advised to upgrade from 7.1 to 7.4?
The best way, in my humble opinion, is to build a new machine, and
install 7.4 or 8.0 on it. Backup the old 7.1 machine us
http://news.zdnet.com/2100-9590_22-5806608.html
Interestingly, in mentioning how unix just unix, they might have
mispelled PostgreSQL, but at least they didn't say "MySQL is MySQL".
It's about halfway through the article.
---(end of broadcast)---
T
On Wed, 2005-07-27 at 12:53, Jim C. Nasby wrote:
> On Wed, Jul 27, 2005 at 04:46:56PM +0200, [EMAIL PROTECTED] wrote:
> > I'm now testing with pg_pool installed on each apache frontend with 260
> > pg_pool preforked clients in each machine.
> >
> > The database seems to work better. At least when
I've been googling a little bit and appears that 7.1 pretty old. What steps are
advised to upgrade from 7.1 to 7.4?
-Jonathan
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
# [EMAIL PROTECTED] / 2005-07-27 10:13:10 -0700:
> On Wed, 27 Jul 2005, Roman Neuhauser wrote:
> > # [EMAIL PROTECTED] / 2005-07-27 10:05:43 -0400:
> > > I am at the design phase of the DB design. That is, I'd like to design
> > > tables and relationships between them, but not the real implement o
On Wed, Jul 27, 2005 at 04:46:56PM +0200, [EMAIL PROTECTED] wrote:
> I'm now testing with pg_pool installed on each apache frontend with 260
> pg_pool preforked clients in each machine.
>
> The database seems to work better. At least when it goes to swap it
> doesn't stop working...
Wait, are y
On Wednesday 27 July 2005 12:30, Alvaro Herrera wrote:
> On Wed, Jul 27, 2005 at 11:46:05AM -0400, Robert Treat wrote:
> > Seems unlikely unless folks like Tom Lane, Stephan Szabo, and Richard
> > Huxton have unsubscribed and resubscribed lately... Funny thing is it
> > isnt every messages, but may
Heh, I have to concur with this comment. Though I always found the US
letter format to be more standards compliant, myself.
On Wed, 27 Jul 2005, Roman Neuhauser wrote:
> # [EMAIL PROTECTED] / 2005-07-27 10:05:43 -0400:
> > Greetings,
> >
> > I am at the design phase of the DB design. That is, I'
Hi Tom,
I solved the problem meanwhile. I was using the SUBSTRING function with
from/length integer arguments. DBD::Pg (this is using perl) binds all
parameters as type VARCHAR by default, so what I had to do was supply
an extra type parameter to the $sth->bind_param() calls so that they
are
On Jul 27, 2005, at 12:09 PM, Scott Marlowe wrote:
On Wed, 2005-07-27 at 10:56, Vivek Khera wrote:
But don't put important data on it since it doesn't do ECC RAM
Considering the small incremental cost of ECC ram, it's hard to
believe
someone would build one of those without it.
Th
The client has to read the incoming data stream for indications of the
type of data that is coming next, then further read a description of
each field name, type, and nullabillity in the event it is a dataset.
It is not pretty. I don't know how the higher level interfaces handle
it, but here is s
On Wed, Jul 27, 2005 at 11:46:05AM -0400, Robert Treat wrote:
> Seems unlikely unless folks like Tom Lane, Stephan Szabo, and Richard
> Huxton have unsubscribed and resubscribed lately... Funny thing is it
> isnt every messages, but maybe half of them. And its not to specific
> users, sometimes on
On Wed, Jul 27, 2005 at 11:46:05 -0400,
Robert Treat <[EMAIL PROTECTED]> wrote:
>
> Seems unlikely unless folks like Tom Lane, Stephan Szabo, and Richard
> Huxton have unsubscribed and resubscribed lately... Funny thing is it
> isnt every messages, but maybe half of them. And its not to specific
On Wed, Jul 27, 2005 at 11:46:05AM -0400, Robert Treat wrote:
> > > Anyone else getting duplicate messages? I seem to be getting them
> > > sporadically on different messages on pgsql-general. Seems to have
> > > started
> > > sometime Monday morning (estern us time)
> >
> > One reason this hap
On Wed, 2005-07-27 at 10:56, Vivek Khera wrote:
> On Jul 26, 2005, at 1:25 PM, Richard Huxton wrote:
>
> > Review
> > http://www.anandtech.com/storage/showdoc.aspx?i=2480
> > Slashdot
> > http://hardware.slashdot.org/article.pl?sid=05/07/26/1229211&tid=198
> >
> > Might be useful for those of us
On Wed, 2005-07-27 at 10:31, Dr NoName wrote:
> > Sure. Like this:
> >
> > Client A accesses table T, and "hangs."
> > Client B attempts to get an ACCESS EXCLUSIVE lock on
> > table T in
> > preparation for VACUUM FULL.
> > Client C connects to the database and waits for
> > client B to get and
>
On Jul 26, 2005, at 1:25 PM, Richard Huxton wrote:
Review
http://www.anandtech.com/storage/showdoc.aspx?i=2480
Slashdot
http://hardware.slashdot.org/article.pl?sid=05/07/26/1229211&tid=198
Might be useful for those of us working with "budget" systems. If
anyone does make a purchase, pleas
thanks.
- Original Message -
From: "Ben Trewern" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, July 26, 2005 7:33 PM
Subject: Re: [GENERAL] PostgreSQL, Lazarus and zeos ?
You need the cvs version of zeoslib to work with Lazarus. It's also the
6.5.something version. The old 5.x only worked
On Wed, 2005-07-27 at 10:09, Greg Sabino Mullane wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> > Anyone else getting duplicate messages? I seem to be getting them
> > sporadically on different messages on pgsql-general. Seems to have started
> > sometime Monday morning (este
> Sure. Like this:
>
> Client A accesses table T, and "hangs."
> Client B attempts to get an ACCESS EXCLUSIVE lock on
> table T in
> preparation for VACUUM FULL.
> Client C connects to the database and waits for
> client B to get and
> release his lock on table T.
> Client D connects to the datab
On Tue, 2005-07-26 at 13:54, DracKewl wrote:
> Trying out PostgreSQL for the first time and running into a minor
> problem.
> I created two tables one with the Add table wizard the other hard-core
> script.
>
> Script made table:
> Select * from Example
> --This works as expected
> Select * from E
Binary backups are not going to work across major releases so just
installing 8.0 with your old cluster won't work.
You'll need to do a pg_dump of your old setup and then restore on your
new cluster.
Hope this helps,
On Wed, Jul 27, 2005 at 12:27:41AM -0400, Mark Mikulec wrote:
> Hi there,
>
>
On Jul 27, 2005, at 10:46 AM, [EMAIL PROTECTED] wrote:
I'm now testing with pg_pool installed on each apache frontend with
260 pg_pool preforked clients in each machine.
Why did you pick 260?
You don't need a 1:1 ratio. That is the point of the pool. Those
connections are "shared". Chanc
I'm now testing with pg_pool installed on each apache frontend with 260
pg_pool preforked clients in each machine.
The database seems to work better. At least when it goes to swap it
doesn't stop working...
I also reduced the shared buffers and moved the pg_xlog folder to
another disk on ano
On Wed, Jul 27, 2005 at 12:45:12PM +1000, Ezequiel Tolnay wrote:
> Ezequiel Tolnay wrote:
> >(...) A function is meant to return a
> >result (or a set of results) of a predefined type *during* execution,
> >whilst a stored procedure (...)
>
> I meant to say *after* instead of *during*. The capabi
Zeos Database Designer is OK.
http://www.zeoslib.net
Tony Caduto
http://www.amsoftwaredesign.com/lightning_admin.php
Home of PG Lightning Admin (PGLA) for Postgresql 8.x
Ying Lu wrote:
Greetings,
I am at the design phase of the DB design. That is, I'd like to design
tables and relationsh
# [EMAIL PROTECTED] / 2005-07-27 10:05:43 -0400:
> Greetings,
>
> I am at the design phase of the DB design. That is, I'd like to design
> tables and relationships between them, but not the real implement of
> tables. Could somebody suggest some good and free tools to help/ease
> design the str
Hi Riaan.!
i think that is a better solution, to use the postgres native type
"serial", that it is a autoincremental number type. You can see it
on the postgres manual. It's very usefull because of you only need to
redifine the type of your id vars. For example, on this moment you
have
CREA
# [EMAIL PROTECTED] / 2005-07-26 14:06:34 -0700:
> BEGIN WORK;
> DECLARE cursor1 CURSOR FOR SELECT * FROM PARTS;
> FETCH FIRST FROM cursor1;
> CLOSE cursor1;
> COMMIT WORK;
>
>
> Query result with 1 rows discarded.
> Query returned successfully with no result in 31 ms.
>
# [EMAIL PROTECTED] / 2005-07-27 10:03:15 -0400:
> Roman Neuhauser wrote:
> ># [EMAIL PROTECTED] / 2005-07-27 08:56:24 -0400:
> >>How does one receive all mail to this list in a daily digest?
> >
> > Have you read the mailing list usage notes on the web site?
>
> set pgsql-general digest
Yes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Anyone else getting duplicate messages? I seem to be getting them
> sporadically on different messages on pgsql-general. Seems to have started
> sometime Monday morning (estern us time)
One reason this happens is because people post to the list
I did a couple of tests and found that occationally when using the
wizard it added "" to my names. When this happens it forces the whole
table to be case sensitive. Anyway I think I'll just stick to manually
creating my tables.
---(end of broadcast)--
Hello,
You can use the information_schema.* tables, which are part of the SQL
standard (and thus not proprietary).
-Mark.
Walsh, Richard (Richard) wrote:
Hi,
I have a problem in that I need to drop non-existent tables in a DDL
script. This is in order that the script can re-build a databas
Greetings,
I am at the design phase of the DB design. That is, I'd like to design
tables and relationships between them, but not the real implement of
tables. Could somebody suggest some good and free tools to help/ease
design the structures please?
Thanks a lot!
Emi
-
set pgsql-general digest
Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2005-07-27 08:56:24 -0400:
How does one receive all mail to this list in a daily digest?
Have you read the mailing list usage notes on the web site?
---(end of broadcast)---
Am Dienstag, 26. Juli 2005 23:53 schrieb Randall Perry:
> Read the Rules section of the manual and the section on Rules vs Triggers.
>
> From what I get triggers are necessary for column constraints. As far as
> speed, it seems there are some differences between how fast rules/triggers
> would do t
Trying out PostgreSQL for the first time and running into a minor
problem.
I created two tables one with the Add table wizard the other hard-core
script.
Script made table:
Select * from Example
--This works as expected
Select * from EXAMPLE
--This works as expected
Wizard made table:
Select * fr
# [EMAIL PROTECTED] / 2005-07-27 08:56:24 -0400:
> How does one receive all mail to this list in a daily digest?
Have you read the mailing list usage notes on the web site?
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't
Ezequiel Tolnay wrote:
(...) A function is meant to return a
result (or a set of results) of a predefined type *during* execution,
whilst a stored procedure (...)
I meant to say *after* instead of *during*. The capabilitie to return
results during execution could only be suported by stored pr
Here is a further test:
--
BEGIN WORK;
DECLARE cursor1 CURSOR FOR SELECT * FROM PARTS;
FETCH FIRST IN cursor1;
INSERT INTO partstemp VALUES (PARTS.QTY, PARTS.LENGTH, PARTS.WIDTH);
CLOSE cursor1;
COMMIT WORK;
--
Hi there,
This may be a stupid question but I feel I should ask it anyway just to be sure, since I've had problems in the past.
I currently have a defunct Debian 3.0 system running PostgreSQL 7.4.1, in
which I am going to do an entire blob backup dump of all the databases
in hopes to restore them
Chris Browne wrote:
kleptog@svana.org (Martijn van Oosterhout) writes:
On Mon, Jul 25, 2005 at 11:35:14AM +1000, Ezequiel Tolnay wrote:
Functions are not the same as stored procedures, but since PG lacks
stored procedures, there is a necessity to use functions instead.
Ok, maybe I'm missing
We have a 7.2.4 postgres database that was bloated. We went
into postgres single user mode to
Vacuum and reindex the database. (postgres -0 –P) We
reindexed a number of indices explicitly.
We now cannot use the database, and are getting e.g.
ERROR: Relation 9262944 does not exist
W
You need the cvs version of zeoslib to work with Lazarus. It's also the
6.5.something version. The old 5.x only worked with Delphi. See the
Lazarus forums for more information.
Ben
>""Zlatko Matiæ"" <[EMAIL PROTECTED]> wrote in message
>news:[EMAIL PROTECTED]
>Hi.
>Someone mentioned Lazar
BEGIN WORK;
DECLARE cursor1 CURSOR FOR SELECT * FROM PARTS;
FETCH FIRST FROM cursor1;
CLOSE cursor1;
COMMIT WORK;
Query result with 1 rows discarded.
Query returned successfully with no result in 31 ms.
In the "data output" view nothing is returned?
> Anyone else getting duplicate messages?
Yep, have been getting them sporadically ever since I
joined (about 5 weeks ago). It's something that
happens once in a while on many mailing lists, I
wouldn't worry about it unless it becomes a regular occurence.
_
On Jul 27, 2005, at 4:22 AM, [EMAIL PROTECTED] wrote:
Already checked.
We set a machine with only pg_pool installed as a fronted to the
real db.
If I disable persistent connections and I use pg_pool with 4096
preforked clients,
no no no.
you don't want 4096 preforked clients.
What you wa
How does one receive all mail to this list in a daily digest?
-Andrew
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Anyone else getting duplicate messages? I seem to be getting them
sporadically on different messages on pgsql-general. Seems to have started
sometime Monday morning (estern us time)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end
Hi Michael,
I am executing these statements inside an SQL DDL script so I think they
all take place inside a single transaction. I am not using PSQL. I will
try what you suggest and see if executing the drop statements in a
separate tx will work.
Richie.
-Original Message-
From: Michael Fu
Thanks for this Mark.
This seems like it will work well for TABLES and VIEWS. However I have
also other categories such as USER, GROUP and TYPE. For these I cant
seem to find out where they are in the information_schema in postgres.
There is no CREATE GROUP statement in the SQL standard, so this
On Tue, Jul 26, 2005 at 06:25:23PM -0300, Adam O'Toole wrote:
> I am searching for a way to have my postgresql 7.4.7 backend be triggered to
> let the front end know there has been a change to the database. If more then
> one person is connected to the database and person (x) makes a change, I wan
# [EMAIL PROTECTED] / 2005-07-27 10:22:48 +0200:
> Richard Huxton wrote:
> >Sounds like a BEGIN being re-issued alright. Solution - fix your
> >application(s) and don't use persistent connections (or if you do,
> >make sure you rollback any pre-existing transactions and issue any
> >relevant SET
1 - 100 of 109 matches
Mail list logo
