Greg Smith wrote:
And if anybody suggests putting a "_" in something I have to type all
the time, I will stick my fingers in my ears and start yelling until
they stop. Bad enough I have to type pg_ctl a few times every day now.
+10 on hating "_"
--
Shane Ambler
pgSQL (at) Sheeky (dot) Biz
I have used batch update in postgres.
for jdbc driver:
A driver that implements batch updates may or may not continue to process
the remaining commands in a batch when one of the commands fails to execute
properly.
then , who can tell which version postgres's jdbc driver that continue to
process th
Brent Wood typed:
> I need to learn to type!!! try PostGIS (how did that become PistGIC? I have
> no idea)
>
> >>> "Brent Wood" <[EMAIL PROTECTED]> 27/03/08 1:44 PM >>>
> Add Informix to the list of IBM's RDBMS products.. Also note that where
> Postgres has PistGIC
> as an OGC compliant geoda
I need to learn to type!!! try PostGIS (how did that become PistGIC? I have
no idea)
>>> "Brent Wood" <[EMAIL PROTECTED]> 27/03/08 1:44 PM >>>
Add Informix to the list of IBM's RDBMS products.. Also note that where
Postgres has PistGIC as an OGC compliant geodata extension, IBM already
suppor
On Mar 26, 2008, at 8:17 PM, Tom Lane wrote:
Whatever would make you think that readline has anything to do with
that?
Just an uneducated guess because long ago not adding that flag
required additional library dependencies. I forgot to include that
when I compiled the first time and there
Add Informix to the list of IBM's RDBMS products.. Also note that where
Postgres has PistGIC as an OGC compliant geodata extension, IBM already
supports this in both DB2 & Informix, so an even higher degree if
interoperability is there for geospatial data.
Brent Wood
>>> Alex Vinogradovs <[E
1) What type of names do you prefer?
---
a) old notation - createdb, createuser ...
b) new one with pg_ prefix - pg_createdb, pg_creteuser ...
c) new one with pg prefix - pgcreatedb, pgcreateuser ...
d) remove them - psql is the solution
e) remove them - pgadmin is th
John DeSoi <[EMAIL PROTECTED]> writes:
> I notice that when I build 8.3.1 psql on OS X (10.5.2) there is now a
> library dependency on /usr/lib/libgcc_s.1.dylib even though I
> specified "--without-readline" in configure.
Whatever would make you think that readline has anything to do with
that
I notice that when I build 8.3.1 psql on OS X (10.5.2) there is now a
library dependency on /usr/lib/libgcc_s.1.dylib even though I
specified "--without-readline" in configure. I don't see this
dependency with psql 8.2. Is there a way to remove this library
requirement in the build? I want
On Wed, 26 Mar 2008, Steve Atkins wrote:
These were mostly rhetorical suggestions. Not serious in themselves,
but hoping to make people come clean about why name changes of
binaries might be needed.
So far I haven't seen anyone besides Zdenek gives a reason why this is
worth the trouble, and
On Wed, Mar 26, 2008 at 03:25:04PM +0100, Zdeněk Kotala wrote:
> Hello All,
>
> I prepared patch for renaming postgreSQL script tools like createdb,
> createuser, etc. to pg_createdb, pg_creteuser. Original names will be kept
> for 2 or 3 following versions. The main reason for the patch is to av
On Wed, 26 Mar 2008 22:46:08 +,
Sam Mason <[EMAIL PROTECTED]> wrote:
[...]
> You could turn the problem around and make the bool columns into ints
> (which should be a simple search-and-replace, I hope) and then write
> something (again hopefully simple) to turn them all back into bools.
> I.
"Adam Rich" <[EMAIL PROTECTED]> writes:
>> Thanks Richard. Is there a way to do it without changing the INSERT
>> command? As I mentioned, there are many more columns of different
>> types, so finding and replacing the VALUES would be very difficult.
> Can you import the data into a holding tabl
On Wed, Mar 26, 2008 at 3:28 PM, Seb <[EMAIL PROTECTED]> wrote:
> On Wed, 26 Mar 2008 15:11:47 -0700,
> "Richard Broersma" <[EMAIL PROTECTED]> wrote:
>
> [...]
>
> > INSERT INTO my_table (var_bool) VALUES ( CAST( 0 AS BOOLEAN )); or
> > INSERT INTO my_table (var_bool) VALUES (0::BOOLEAN);
>
>
> Th
On Wed, 26 Mar 2008 17:34:59 -0500,
"Adam Rich" <[EMAIL PROTECTED]> wrote:
[...]
> Can you import the data into a holding table (with columns defined as
> integer) first, and then use a SQL statement to insert from there into
> the final destination table (casting in the process) ?
Yes, that wou
On Wed, Mar 26, 2008 at 05:28:18PM -0500, Seb wrote:
> On Wed, 26 Mar 2008 15:11:47 -0700,
> "Richard Broersma" <[EMAIL PROTECTED]> wrote:
>
> [...]
>
> > INSERT INTO my_table (var_bool) VALUES ( CAST( 0 AS BOOLEAN )); or
> > INSERT INTO my_table (var_bool) VALUES (0::BOOLEAN);
>
>
> Thanks Ric
> Thanks Richard. Is there a way to do it without changing the INSERT
> command? As I mentioned, there are many more columns of different
> types, so finding and replacing the VALUES would be very difficult.
Can you import the data into a holding table (with columns defined
as integer) first, an
On Wed, 26 Mar 2008 15:11:47 -0700,
"Richard Broersma" <[EMAIL PROTECTED]> wrote:
[...]
> INSERT INTO my_table (var_bool) VALUES ( CAST( 0 AS BOOLEAN )); or
> INSERT INTO my_table (var_bool) VALUES (0::BOOLEAN);
Thanks Richard. Is there a way to do it without changing the INSERT
command? As I
On Wed, Mar 26, 2008 at 2:58 PM, Seb <[EMAIL PROTECTED]> wrote:
> INSERT INTO my_table (var_bool) VALUES (0);
> INSERT INTO my_table (var_bool) VALUES (1);
>
> So this results in an error. Unfortunately, there are many more columns
> and it would be very difficult to write a regexp to replace the
Hi,
I'm running into a problem importing some MS Access tables into
PostgreSQL using mdbtools. The schema is exported effectively with
mdb-schema, but several tables have boolean columns. To deal with some
embedded double quotes in text fields, I'm exporting the tables as
INSERT commands using m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Online registration for East closes at 5:00pm PST. However you still
can register *at the door*. If you wish to register at the door, please
bring a check made out to the Following:
Software In the Public Interest
In the memo field put:
Post
[EMAIL PROTECTED] (Steve Atkins) writes:
> There are no existing clashes with system tools that I'm aware of. Are
> there any? Most of the clashes are with other installations of
> postgresql installed on the same machine, so if name clashes is the
> real reason for the change, then the version num
Zdenek Kotala wrote:
> One of my original idea was to create pg_cmd command which will integrate
> all create/drop command in one. For example
>
> pg_cmd create database
> pg_cmd list user
>
> and so on.
I do like this idea, though I don't like the pg_cmd name, because it
conflicts with pg_ctl o
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> I like this too. It'd be considerably more work than the currently
>> proposed patch, though, since we'd have to meld the currently
>> separate programs into one executable.
> I note that we can continue to have the current executabl
1) What type of names do you prefer?
---
b) new one with pg_ prefix - pg_createdb, pg_creteuser ...
2) How often do you use these tools?
---
b) one per week
3) What name of initdb do you prefer?
-- --
b)
Alvaro Herrera napsal(a):
Tom Lane wrote:
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
On Wednesday 26. March 2008, Ron Mayer wrote:
I'd prefer a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
I'll second that. It would be much easie
Ron Mayer napsal(a):
Zdeněk Kotala wrote:
1) What type of names do you prefer?
I'd prefer a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
There are many precedents. "cvs update", "git pull"
"apt-get install".
Anyone else like this ap
Tom Lane napsal(a):
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
On Wednesday 26. March 2008, Ron Mayer wrote:
I'd prefer a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
I'll second that. It would be much easier on the brain, as yo
Ron Mayer napsal(a):
Tom Lane wrote:
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
On Wednesday 26. March 2008, Ron Mayer wrote:
...a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
I'll second that. ...
I like this too.
Though
On Wed, Mar 26, 2008 at 10:02:45AM -0700, Steve Atkins wrote:
> What's the psql equivalent of the "standard" use case of "vacuumdb -a"?
> (If you don't know the answer, for both unix and windows, you don't get
> to vote for removing vacuumdb).
linux:
psql -qAt -c "select E'connect ' || datnam
Tom Lane wrote:
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
On Wednesday 26. March 2008, Ron Mayer wrote:
...a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
I'll second that. ...
I like this too.
Though I guess we might need
Le Wednesday 26 March 2008 15:25:04 Zdeněk Kotala, vous avez écrit :
> 1) What type of names do you prefer?
> ---
>
> a) old notation - createdb, createuser ...
> b) new one with pg_ prefix - pg_createdb, pg_creteuser ...
> c) new one with pg prefix - pgcreatedb, pgcreat
On Wednesday 26 March 2008 16:25, Zdeněk Kotala wrote:
> 1) What type of names do you prefer?
> ---
b) new one with pg_ prefix - pg_createdb, pg_creteuser ...
>
> 2) How often do you use these tools?
> ---
>
b) one per week
>
>
> 3) W
Tom Lane wrote:
> "Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
> > On Wednesday 26. March 2008, Ron Mayer wrote:
> >> I'd prefer a "pg" program that took as arguments
> >> the command. So you'd have "pg createdb" instead
> >> of "pg_createdb".
>
> > I'll second that. It would be much easier o
Brad Nicholson <[EMAIL PROTECTED]> writes:
> We just took a test database down (PG 8.1.11) fairly hard (pulled a SAN
> switch out while it was under load), which caused the DB to crash. It
> started up fine, when I vacuumed the DB, I saw the following messages.
> WARNING: relation "my_table" pag
Tom Lane wrote:
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
On Wednesday 26. March 2008, Ron Mayer wrote:
I'd prefer a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
I like this too. It'd be considerably more work than the current
Brad Nicholson wrote:
> We just took a test database down (PG 8.1.11) fairly hard (pulled a SAN
> switch out while it was under load), which caused the DB to crash. It
> started up fine, when I vacuumed the DB, I saw the following messages.
>
> WARNING: relation "my_table" page 652139 is uniniti
- Original Message -
From: Zden?k Kotala <[EMAIL PROTECTED]>
Date: Wednesday, March 26, 2008 10:25 am
Subject: [GENERAL] Survey: renaming/removing script binaries
(createdb, createuser...)
> Hello All,
>
> I prepared patch for renaming postgreSQL script tools like
> createdb, createuser
On Mar 26, 2008, at 11:44 AM, Leif B. Kristensen wrote:
On Wednesday 26. March 2008, Ron Mayer wrote:
I'd prefer a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
There are many precedents. "cvs update", "git pull"
"apt-get install".
An
"Leif B. Kristensen" <[EMAIL PROTECTED]> writes:
> On Wednesday 26. March 2008, Ron Mayer wrote:
>> I'd prefer a "pg" program that took as arguments
>> the command. So you'd have "pg createdb" instead
>> of "pg_createdb".
> I'll second that. It would be much easier on the brain, as you might
> i
Shouldn't forget IBM got DB2. Could be they are
just seeking additional userbase in opensource
market space...
On Wed, 2008-03-26 at 12:12 -0700, Ron Mayer wrote:
> Clodoaldo wrote:
> > ...IBM is investing...What does it mean for Postgresql?
>
> One cool thing it means is that there are now *two
Sam Mason wrote:
Looks like you've "disabled" seqscans.
Sure enough. Thanks.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
We just took a test database down (PG 8.1.11) fairly hard (pulled a SAN
switch out while it was under load), which caused the DB to crash. It
started up fine, when I vacuumed the DB, I saw the following messages.
WARNING: relation "my_table" page 652139 is uninitialized --- fixing
WARNING: rela
On Wed, 26 Mar 2008 12:12:48 -0700
Ron Mayer <[EMAIL PROTECTED]> wrote:
> Clodoaldo wrote:
> > ...IBM is investing...What does it mean for Postgresql?
>
> One cool thing it means is that there are now *two*
> companies (thanks again Fujitsu) bigger than
> Oracle backing (to some extent) Postgres.
Clodoaldo wrote:
...IBM is investing...What does it mean for Postgresql?
One cool thing it means is that there are now *two*
companies (thanks again Fujitsu) bigger than
Oracle backing (to some extent) Postgres.
And now one company bigger than Microsoft.
Yeah, this doesn't affect the communit
On Mar 26, 2008, at 12:06 PM, Tom Lane wrote:
Steve Atkins <[EMAIL PROTECTED]> writes:
On Mar 26, 2008, at 10:46 AM, Alvaro Herrera wrote:
Steve Atkins wrote:
"pg_ctl" to "safe_postgresqld",
Now that's plain weird.
Yes, it is. But if the goal is to make it more approachable for
people
Steve Atkins <[EMAIL PROTECTED]> writes:
> On Mar 26, 2008, at 10:46 AM, Alvaro Herrera wrote:
>> Steve Atkins wrote:
>>> "pg_ctl" to "safe_postgresqld",
>>
>> Now that's plain weird.
> Yes, it is. But if the goal is to make it more approachable for people
> who are familiar with mysql, but not p
Alvaro Herrera wrote:
Steve Atkins wrote:
There are no existing clashes with system tools that I'm aware of. Are
there any? Most of the clashes are with other installations of
postgresql installed on the same machine, so if name clashes is the real
reason for the change, then the version nu
1. b
2. a
3. b (must be consistent with 1st question prefix)
4. c, b
Bruno Lavoie
Zdeněk Kotala a écrit :
Hello All,
I prepared patch for renaming postgreSQL script tools like createdb,
createuser, etc. to pg_createdb, pg_creteuser. Original names will be
kept for 2 or 3 following versions.
On Wed, 26 Mar 2008, Zdeněk Kotala <[EMAIL PROTECTED]> writes:
> 1) What type of names do you prefer?
> ---
> b) new one with pg_ prefix - pg_createdb, pg_creteuser ...
OTOH,
> d) remove them - psql is the solution
> 2) How often do you use these tools?
>
On Wednesday 26. March 2008, Ron Mayer wrote:
>I'd prefer a "pg" program that took as arguments
>the command. So you'd have "pg createdb" instead
>of "pg_createdb".
>
>There are many precedents. "cvs update", "git pull"
>"apt-get install".
>
>Anyone else like this approach?
I'll second that. It
On Wed, Mar 26, 2008 at 01:23:22PM -0500, Jeff Amiel wrote:
> explain analyze select * from table_a;
> "Seq Scan on table_a (cost=1.00..10001.02 rows=19
> width=103) (actual time=0.007..0.012 rows=19 loops=1)"
> "Total runtime: 0.040 ms"
>
> any ideas?
Looks like you've "disabled" se
And yes...I vacuumed...analyzed...vacuum analyzed the table to no avail.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Only 19 rows in the table.
explain analyze select * from table_a;
"Seq Scan on table_a (cost=1.00..10001.02 rows=19
width=103) (actual time=0.007..0.012 rows=19 loops=1)"
"Total runtime: 0.040 ms"
If I run the same query on the same table in a different database that I
pg_res
On Wed, 26 Mar 2008 11:09:48 -0700
Steve Atkins <[EMAIL PROTECTED]> wrote:
> Yes, it is. But if the goal is to make it more approachable for
> people who
> are familiar with mysql, but not prepared to read postgresql
> documentation
> it's also the obvious change to make.
I would note that sys
Sorry, I didn't realize what you were asking.
[local]:owl=# SHOW TimeZone;
TimeZone
--
EST5EDT
(1 row)
Tom Lane wrote:
Joseph S <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Works for me ... what have you got TimeZone set to?
/etc/localtime -> /usr/share/zoneinfo/US/Eastern
Yo
On 26/03/2008, Zdeněk Kotala <[EMAIL PROTECTED]> wrote:
> Hello All,
>
> I prepared patch for renaming postgreSQL script tools like createdb,
> createuser,
> etc. to pg_createdb, pg_creteuser. Original names will be kept for 2 or 3
> following versions. The main reason for the patch is to avoid
On Mar 26, 2008, at 10:46 AM, Alvaro Herrera wrote:
Steve Atkins wrote:
There are no existing clashes with system tools that I'm aware of.
Are
there any? Most of the clashes are with other installations of
postgresql installed on the same machine, so if name clashes is the
real
reason for
Chris Browne wrote:
> I seem to recall there being a relevant Google Summer of Code project
> about this, last year.
> I do not recall how far it got. It obviously didn't make it into 8.3
> ;-)!
Some parts of it did -- for example we got "read-only transactions"
which were a step towards that g
Zdeněk Kotala wrote:
1) What type of names do you prefer?
I'd prefer a "pg" program that took as arguments
the command. So you'd have "pg createdb" instead
of "pg_createdb".
There are many precedents. "cvs update", "git pull"
"apt-get install".
Anyone else like this approach?
Of the choice
Steve Atkins wrote:
> There are no existing clashes with system tools that I'm aware of. Are
> there any? Most of the clashes are with other installations of
> postgresql installed on the same machine, so if name clashes is the real
> reason for the change, then the version number or port num
Joseph Shraibman <[EMAIL PROTECTED]> writes:
> Sorry, I didn't realize what you were asking.
> [local]:owl=# SHOW TimeZone;
> TimeZone
> --
> EST5EDT
> (1 row)
[ squint... ] That should certainly think that we're into DST;
it does here:
regression=# set timezone = 'EST5EDT';
SET
regr
On Wed, 26 Mar 2008, Zdenk Kotala wrote:
1) What type of names do you prefer?
---
b) new one with pg_ prefix - pg_createdb, pg_creteuser ...
2) How often do you use these tools?
---
b) one per week
3) What name of initdb do you pr
After I sent my last email, a light bulb went off. I remembered a
similar problem I had a while ago with parts of postgres not having read
permission. Sure enough after I
[EMAIL PROTECTED] /usr/local/pgsql]# chmod -R a+r *
then restart postgres everything is fine.
This is a IMHO a bug in th
At 11:04a -0400 on Wed, 26 Mar 2008, Ivan Sergio Borgonovo wrote:
> - maybe a pg[something] action may be better integrated with
> bash auto-completion without rewriting a sql parser
$ cat ~/.hypothetical_bashrc
...
complete -o default -F postgres_completion_function pg_cmd
...
$ pg_cmd
CREAT
On Wednesday 26 March 2008, Zdeněk Kotala <[EMAIL PROTECTED]> wrote:
> 1) What type of names do you prefer?
> ---
>
> a) old notation - createdb, createuser ...
> b) new one with pg_ prefix - pg_createdb, pg_creteuser ...
> c) new one with pg prefix - pgcreatedb, pgcreat
On Mar 26, 2008, at 7:25 AM, Zdeněk Kotala wrote:
Hello All,
I prepared patch for renaming postgreSQL script tools like createdb,
createuser, etc. to pg_createdb, pg_creteuser. Original names will
be kept for 2 or 3 following versions. The main reason for the patch
is to avoid possible cl
Joseph S <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Works for me ... what have you got TimeZone set to?
> /etc/localtime -> /usr/share/zoneinfo/US/Eastern
You didn't answer the question: what does "SHOW TimeZone" say?
regards, tom lane
--
Sent via pgsql-general
At 10:25a -0400 on Wed, 26 Mar 2008, Zdeněk Kotala wrote:
> And after long discussion on patches and hackers list we have made a
> decision than we need input from wide audience. This is a reason why
> I prepare following surveys.
1. b
2. b
3. b (but whichever, just be consistent)
4. b & c
I don'
On Mar 26, 2008, at 9:37 AM, björn lundin wrote:
1) What type of names do you prefer?
d) remove them - psql is the solution
2) How often do you use these tools?
a) every day (e.g. in my cron)
3) What name of initdb do you prefer?
d) pg_ctl -d init (replace initdb with pg_ctl new
function
1) What type of names do you prefer?
---
a) old notation - createdb, createuser ...
b) new one with pg_ prefix - pg_createdb, pg_creteuser ...
c) new one with pg prefix - pgcreatedb, pgcreateuser ...
d) remove them - psql is the solution
e) remove them - pgadmin is the
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> Weirdly, I'm getting the right offsets, but my timezone in pgsql is
> navajo... For the OS it's America/Denver like I set it. And there's
> no timezone set in postgresql.conf.
According to the TZ files, "Navajo" is just an alias for
"America/Denver":
> 1) What type of names do you prefer?
> d) remove them - psql is the solution
>
> 2) How often do you use these tools?
> a) every day (e.g. in my cron)
> 3) What name of initdb do you prefer?
> d) pg_ctl -d init (replace initdb with pg_ctl new functionality)
> 4) How do you perform VACUUM?
> a
On Tue, Mar 25, 2008 at 5:39 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Joseph S <[EMAIL PROTECTED]> writes:
> > Was there something wrong with the tzdata distributed in 8.2.7?
> > current_timestamp is still using EST, but the date command run from the
> > command line is correctly returning EDT
-- Forwarded message --
From: Joey K. <[EMAIL PROTECTED]>
Date: Wed, Mar 26, 2008 at 9:42 AM
Subject: Re: [GENERAL] Survey: renaming/removing script binaries (createdb,
createuser...)
To: Zdeněk Kotala <[EMAIL PROTECTED]>
Please let us know your meaning,
>
>thanks
Anton Andreev wrote:
Hi,
Thank you for you detailed answer, but I am exactly in the case when I
want to paste the script and hit F5 and have both the database and
tables created.
>
A problem also comes from the fact that in order to use the query window
in pgadmin3, you need to select a data
[EMAIL PROTECTED] (Keaton Adams) writes:
> That is an interesting question. If our organization were to help fund the
> development of such a feature, would that be something taken into
> consideration by the development team?
I seem to recall there being a relevant Google Summer of Code project
Tom Lane wrote:
Joseph S <[EMAIL PROTECTED]> writes:
Was there something wrong with the tzdata distributed in 8.2.7?
current_timestamp is still using EST, but the date command run from the
command line is correctly returning EDT
Works for me ... what have you got TimeZone set to?
Zdeněk Kotala <[EMAIL PROTECTED]> writes:
> 1) What type of names do you prefer?
>
> d) remove them - psql is the solution
>
>
> 2) How often do you use these tools?
>
> d) never
>
>
> 3) What name of initdb do you prefer?
>
> a) initdb
>
>
> 4) How do you perform VACUUM?
>
> b) VACUUM - SQL comm
1.) b
2.) a
3.) b
4.) a+c
On Wed, 26 Mar 2008 15:25:04 +0100 Zden__k Kotala <[EMAIL PROTECTED]> thought
long, then sat down and wrote:
> Hello All,
>
> I prepared patch for renaming postgreSQL script tools like createdb,
> createuser,
> etc. to pg_createdb, pg_creteuser. Original names will b
> 1) What type of names do you prefer?
> ---
a.
> 2) How often do you use these tools?
> ---
b.
> 3) What name of initdb do you prefer?
> -- --
d.
> 4) How do you perform VACUUM?
>
1. b
2. c
3. d
4. b and c
I do most of my admin using SQL these days. my preference would be
towards keeping them because they're nice in the beginning.
Sam
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.o
Welcome news to have a solid backer..
Any plans for integration with Websphere?
Thanks
Martin
- Original Message -
From: "Bruce Momjian" <[EMAIL PROTECTED]>
To: "Clodoaldo" <[EMAIL PROTECTED]>
Cc: "PostgreSQL - General ML"
Sent: Wednesday, March 26, 2008 9:36 AM
Subject: Re: [GENERAL] IBM
1. b
2. b
3. b
4. c
---
Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
[EMAIL PROTECTED]
---
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.o
On Wed, 26 Mar 2008 15:25:04 +0100
Zdeněk Kotala <[EMAIL PROTECTED]> wrote:
> Please let us know your meaning,
I hope it is the right place where to post.
> 1) What type of names do you prefer?
> c) new one with pg prefix - pgcreatedb, pgcreateuser ...
I'd like the idea of having one command +
1) b
2) c
3) d
4) b & c
--
Mailed by:
UnReAl4U - unreal4u
ICQ #: 54472056
www: http://www.chilehardware.com/
Zdeněk Kotala escribió:
Hello All,
I prepared patch for renaming postgreSQL script tools like createdb,
createuser, etc. to pg_createdb, pg_creteuser. Original names will be
kept for 2 or 3 following versions. The main reason for the patch is
to avoid possible clash of names with systems tool
Zdeněk Kotala wrote:
1) What type of names do you prefer?
---
a) old notation - createdb, createuser ...
b) new one with pg_ prefix - pg_createdb, pg_creteuser ...
c) new one with pg prefix - pgcreatedb, pgcreateuser ...
d) remove them - psql is the solution
e) remove
On Wed, Mar 26, 2008 at 7:19 AM, Clodoaldo
<[EMAIL PROTECTED]> wrote:
> According to Slashdot IBM is investing in EnterpriseDB. What does it
> mean for Postgresql?
There where 2 or 3 blogs posted on the PostgreSQL main page on this
subject that were interesting.
--
Regards,
Richard Broersma Jr.
Clodoaldo wrote:
> According to Slashdot IBM is investing in EnterpriseDB. What does it
> mean for Postgresql?
There should be no affect on the community, except that EnterpriseDB
might be able to support the community a little better because of a
little more funding.
--
Bruce Momjian <[EMAIL
On Wed, Mar 26, 2008 at 2:19 PM, Clodoaldo
<[EMAIL PROTECTED]> wrote:
> According to Slashdot IBM is investing in EnterpriseDB. What does it
> mean for Postgresql?
In a nutshell? It helps EnterpriseDB continue to employ people like
me, Bruce, Heikki, Greg, Pavan and the various other people from
>
> Please let us know your meaning,
>
> thanks Zdenek Kotala
>
1. c
2. a
3. other = "pginitdb", to be consistent with pgcreatedb,etc
4. a
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mai
Hello All,
I prepared patch for renaming postgreSQL script tools like createdb, createuser,
etc. to pg_createdb, pg_creteuser. Original names will be kept for 2 or 3
following versions. The main reason for the patch is to avoid possible clash of
names with systems tools.
And after long discu
According to Slashdot IBM is investing in EnterpriseDB. What does it
mean for Postgresql?
Regards, Clodoaldo Pinto Neto
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
2008/3/26, Alvaro Herrera <[EMAIL PROTECTED]>:
> Clodoaldo escribió:
>
>
> > The database performance slowly degrades and after two weeks i issue a
> > reindex on the database and the performance gets back to normal. I
> > have been doing this for ages and i don't remember in which version
> >
On Mar 26, 2008, at 8:59 AM, josep porres wrote:
INSERT INTO demo_tab SELECT demo_tab_row.*;
I tried this before with no success.
But I realized that it was because a problem with a constraint, no
warnings about this at all.
With the detailed insert i've got the constraint error.
I was us
On Wed, Mar 26, 2008 at 01:03:34AM -0400, Greg Smith wrote:
> against. People who are using the current warm-standby code are already
> grappling with issues like how to coordinate master/slave failover
> (including my second favorite acronym, STONITH for "shoot the other node
> in the head").
Clodoaldo escribió:
> The database performance slowly degrades and after two weeks i issue a
> reindex on the database and the performance gets back to normal. I
> have been doing this for ages and i don't remember in which version
> this degradation behavior appeared, perhaps 8.0 I'm not sure.
W
srdjan wrote:
>>> -- I've got 2 tables and one view
>>> CREATE TABLE a (name varchar(20) primary key, num integer);
>>> CREATE TABLE b (town varchar(15), name varchar(20) references a(name));
>>>
>>> insert into a values ('tom',5);
>>> insert into a values ('paul',99);
>>> insert into a value
Daniel Verite wrote:
Justin wrote:
Another option is use SQL pass through to append records from ACCESS
table into Postgres table that is open in Access.
http://support.microsoft.com/kb/303968
http://msdn2.microsoft.com/en-us/library/bb208861.aspx
the command would look something like th
1 - 100 of 127 matches
Mail list logo
