David Pratt <[EMAIL PROTECTED]> writes:
> I just want to get this right because it will be an important part of what I
> am
> preparing. Sorry for the really long message but I don't know if it would
> make
> any sense if I did not fully explain what i am wanting to do. I am not french
> so ex
On Thu, Jun 16, 2005 at 07:54:29PM -, Greg Sabino Mullane wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I recently submitted a patch that makes all the database objects
> behave in the same way as far as the backslash psql commands.
> Currently, tables work like this: \dt lis
I am interested in having some internationalization capability to an
application. i18 will take care of the interface but not the data. To
internationalize the data, I am wanting to put the internationalized
text strings in a multi_language table like this:
CREATE TABLE multi_language (
On Thu, 16 Jun 2005, Greg Sabino Mullane wrote:
I recently submitted a patch that makes all the database objects behave
in the same way as far as the backslash psql commands. Currently, tables
work like this: \dt lists all non-system tables in your path, while
\dtS shows only the system tables.
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> I maintain that it makes more sense for those few people who regularly look
> at system functions to add a "S" than to have everyone else have to do
> things such as "\df public."
@@aol(me too).
fwiw, i think "few" may be a bit optimistic her
"Matthew T. O'Connor" writes:
> There has been extensive conversation in the last few days, however I
> think Brandon is referencing pgavd which is a project on gborg, which
> was an autovacuum implementation started by someone else that never
> took off. This is totally separate from pg_autovac
I seem to have a problem CC: the list these days...
--- Collin Peters <[EMAIL PROTECTED]> wrote:
>
> Running the query 'EXPLAIN ANALYZE SELECT * FROM pp_users'
> ---
>"Seq Scan on pp_users (cost=0.00..1597.26 rows=37326 width=1102)
> (
Collin Peters wrote:
> The table in question is a simple users table. The details are at the
> bottom of this message. The performance on this table was fine during
> testing with less than 100 users. Then we inserted about 37,000 records
> into the table. Now a 'SELECT * FROM pp_users' takes o
What's at the top and bottom of that?
>PG prints out a memory stats dump like this when it runs out of memory.
>The dump itself isn't much use to anyone but a developer; what you want
>to look into is what triggered it. The error message appearing just
>after (or maybe just before, I forget) shou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I recently submitted a patch that makes all the database objects behave
in the same way as far as the backslash psql commands. Currently, tables
work like this: \dt lists all non-system tables in your path, while
\dtS shows only the system tables. Th
Done. Thanks.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>;
Sent: Thursday, June 16, 2005 3:06 PM
Subject: Re: [GENERAL] pg_dumpall
On 16 Jun 2005 at 11:36, Zlatko Matic wrote:
Ok. but I have a problem. When i double-click, a black window appears,
prompti
Done. Thanks.
- Original Message -
From: "Sean Davis" <[EMAIL PROTECTED]>
To: "Zlatko Matić" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, June 16, 2005 11:51 AM
Subject: Re: [GENERAL] pg_dumpall
See:
http://www.postgresql.org/docs/8.0/static/app-pg-dumpall.html
If you need more specifics
The table in question is a simple users table. The details are at the
bottom of this message. The performance on this table was fine during
testing with less than 100 users. Then we inserted about 37,000 records
into the table. Now a 'SELECT * FROM pp_users' takes over 40 seconds!!.
37,000
On 6/16/05, Cedric BRINER <[EMAIL PROTECTED]> wrote:
> hi,
>
> I'm facing this problem
>
> DROP TABLE test;
> DROP TABLE new_test;
> CREATE TABLE test (id serial NOT NULL UNIQUE, nom varchar(32));
> INSERT INTO test ("nom") values ('cedric');
> INSERT INTO test ("nom") values ('felix');
> INSERT
hi,
I'm facing this problem
DROP TABLE test;
DROP TABLE new_test;
CREATE TABLE test (id serial NOT NULL UNIQUE, nom varchar(32));
INSERT INTO test ("nom") values ('cedric');
INSERT INTO test ("nom") values ('felix');
INSERT INTO test ("nom") values ('julien');
CREATE TABLE new_test (id serial NO
Douglas McNaught wrote:
"Brandon Metcalf" <[EMAIL PROTECTED]> writes:
I've been looking at the auto vacuum daemon pgavd and it looks like
there hasn't been any development activity in a while. Does anyone
know that status of pgavd?
Also, I'd be interested in hearing how well it works and
d == [EMAIL PROTECTED] writes:
d> "Brandon Metcalf" <[EMAIL PROTECTED]> writes:
d> > I've been looking at the auto vacuum daemon pgavd and it looks like
d> > there hasn't been any development activity in a while. Does anyone
d> > know that status of pgavd?
d> >
d> > Also, I'd be interested
"Brandon Metcalf" <[EMAIL PROTECTED]> writes:
> I've been looking at the auto vacuum daemon pgavd and it looks like
> there hasn't been any development activity in a while. Does anyone
> know that status of pgavd?
>
> Also, I'd be interested in hearing how well it works and if there are
> any pla
I've been looking at the auto vacuum daemon pgavd and it looks like
there hasn't been any development activity in a while. Does anyone
know that status of pgavd?
Also, I'd be interested in hearing how well it works and if there are
any plans to include this daemon in the pgsql distribution.
--
"Christopher J. Bottaro" <[EMAIL PROTECTED]> writes:
> $ pg_restore -C -d test_backup_db backup.pgd
> pg_restore: [archiver (db)] connection to database "test_backup_db" failed:
> FATAL: database "test_backup_db" does not exist
> What am I doing wrong? Thank you for the help.
Trying to connect
Here's what I'm trying to do:
$ pg_dump -Fc -b -f backup.pgd test_backup_db
$ dropdb test_backup_db
DROP DATABASE
$ pg_restore -C -d test_backup_db backup.pgd
pg_restore: [archiver (db)] connection to database "test_backup_db" failed:
FATAL: database "test_backup_db" does not exist
Here is what
"Ilja Golshtein" <[EMAIL PROTECTED]> writes:
> To be honest, I don't quite understand why PG does 'send' again and again,
> while
> EPIPE seems to be unrecoverable.
> Isn't it better to terminate server process?
No. See previous discussions in the archives.
(One point is that a long-running qu
"Ilja Golshtein" <[EMAIL PROTECTED]> writes:
> PG Doc 49.2 says: "Each TOAST-able data type specifies a default strategy for
> columns of that data type". How one can find out these default strategies?
Look in pg_type, specifically the typstorage column.
Offhand I think NUMERIC is the only one t
>> Are PG admins experienced in determining and killing such zombi-sessions?
>> I mean, may be script or something to do this job exist in nature?
>> > Thanks.
>>
>
>#statement_timeout = 0 # 0 is disabled, in milliseconds
>
>I think if you give this item in postgresql.conf a value, it wil
> Are PG admins experienced in determining and killing such zombi-sessions?
> I mean, may be script or something to do this job exist in nature?
> > Thanks.
>
#statement_timeout = 0 # 0 is disabled, in milliseconds
I think if you give this item in postgresql.conf a value, it will kill
l
>Tom Lane <[EMAIL PROTECTED]> writes:
>If so, I would bet that someone did an unconstrained join (ie SELECT
>the cross product of some large tables) and killed their client instead
>of waiting for the result.
Quite probably if you recall my Yesterday's question about low
speed of queries with m
Simon Riggs <[EMAIL PROTECTED]> writes:
> Your suggested fix to the 2000+ inherited relation problem seemed like
> it would apply to an area that most people would never use, yet would
> have an effect on anybody using LockAcquire.
Just FYI, the proposed fix is already in, and I think it's a net w
"Ilja Golshtein" <[EMAIL PROTECTED]> writes:
> At the moment on my Linux box I have process
> 'postmaster' eats all CPU. It corresponds
> with connection closed day before -
> not sure if it was normal disconnect.
> strace shows the process constantly
> makes 'send' syscall with EPIPE result.
>I am choosing the best (fastest and smallest) datatype for
>storing some 16-byte length application-level binary
>identifiers.
Addition.
I've SET STORAGE of this column to PLAIN and speed increased about 20%. Any
drawbacks of this trick?
PG Doc 49.2 says: "Each TOAST-able data type specifies a
Hi!
At the moment on my Linux box I have process
'postmaster' eats all CPU. It corresponds
with connection closed day before -
not sure if it was normal disconnect.
strace shows the process constantly
makes 'send' syscall with EPIPE result.
Any ideas how to trace this issue
and/or prevent
On Jun 16, 2005, at 6:21 AM, Craig Bryden wrote:
Hi
I am trying to get information on how to do "Dynamic SQL" in PostgreSQL
(preferably pg/plsql).
Please can someone give an exaple of how this is done or direct me to
the
relevant documentation.
There is searchable documentation here (book
Hello,
I would like to analyze PostgreSQL (8.x) system log for slow queries etc.
Does anybody know any log analyzer, which works under Windows XP?
Thanks for replies.
--
Jiří Němec, ICQ: 114651500
www.menea.cz - www stránky a aplikace
---(end of broadcast)-
On Thu, 2005-06-16 at 00:55 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > Looks bad... but how does it look for 1000 inherited relations? My
> > feeling is that we should not be optimizing the case above 1000
> > relations. That many partitions is very unwieldy.
>
> Well, it
Hi
I am trying to get information on how to do "Dynamic SQL" in PostgreSQL
(preferably pg/plsql).
Please can someone give an exaple of how this is done or direct me to the
relevant documentation.
Thanks
Craig
---(end of broadcast)---
TIP 5: Have y
Per-database user, right, that's what I need...hope it will be included in
future releases...
Separating the power to create new users from the power of being superuser,
also. It is very important.
Greetings,
Zlatko
- Original Message -
From: "Richard Huxton"
To: "Tom Lane" <[EMAIL
On Jun 15, 2005, at 9:47 PM, Jamie Deppeler wrote:
This is a simple question what is the best way to execute a SQL
script, this script will create schemas and tables for a database i
created.
Nearly all clients or interfaces provide a means to execute arbitrary
SQL. You can do so in PgAd
See:
http://www.postgresql.org/docs/8.0/static/app-pg-dumpall.html
If you need more specifics, you will probably need to give more
specifics like OS and version.
Sean
On Jun 16, 2005, at 5:16 AM, Zlatko Matić wrote:
How to start pg_dumpall ?
---(end of broadcast)-
How to start pg_dumpall
?
Am Montag, den 13.06.2005, 11:42 -0400 schrieb Chris Browne:
> [EMAIL PROTECTED] (Tatsuo Ishii) writes:
> >> For the contents too. I dont think the source code installation
> >> should be so much in the focus of the certification.
> >
> > Since PostgreSQL is an open source database, I think it is i
On Thu, 2005-06-16 at 12:59 +0800, Christopher Kings-Lynne wrote:
> > Well, it's not so much that I care about queries with 1000+ relations,
> > as that this is a good way to stress-test the code and find out where
> > the performance issues are. There are many thousand lines of code that
> > can
Dear all,
I have a problem with registering a postgreSQL Server
on windows. I am using PostgreSQL 8.0 on windows xp.
I created a second database cluster using
C:\ProgramFiles\PostgreSQL\8.0\bin>initdb -D
--locale=C E:\DataFiles\PostgreSQL\
8.0\dbc-2
Now I try to register the server in the windo
"Tom Lane" <[EMAIL PROTECTED]> writes:
>
> He's right, you're not: that check is only applied in the
> password-based authorization path.
>
> This has always seemed a bit bogus to me too --- would not object to
> a well-thought-out patch to change it.
>
If we add a "VALID UNTIL" column in pg_hba.
On Thu, 2005-06-16 at 01:10 -0400, Greg Stark wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
>
> > If you really do need that many, you can go to the trouble of grouping
> > them in two levels of nesting, so you have a root table, multiple month
> > tables and then each month table with multiple
43 matches
Mail list logo
