John Gage wrote:
Posters are correctly referred to the documentation as frequently as
possible. In fact, very frequently. The frequency might decrease if
the documentation were in plain text. It is easier to search a single
plain text file than any other source, except perhaps the database
1) On a list that howls with complaints when posts are in html, it is
surprising that there is resistance to the idea of documentation in
plain text.
2) Posters are correctly referred to the documentation as frequently
as possible. In fact, very frequently. The frequency might decrease
Andy Colson wrote:
>> thanks very much Andy. Very elegant.
>> I do need to presere the users that have<5 entries though, so I think I can
>> modify your function to do that as well.
> Oh, duh! because nothing is less than 1900-01-01... my
> date math sucks. It should probably return '2100-01
On Tue, Jun 8, 2010 at 2:01 PM, uaca man wrote:
>> You will have to write your code to be more event
>>driven, and make the web server just generate requests and view the
>>results where they are stored.
>
> What do you mean? That is what I think I am trying to do. No?
You have work you need done
>Hi. What does "PGDG" mean, as in PGDG84, the PostgreSQL >repository
containing PostgreSQL 8.4.x, etc?
Postgresql Global Development Group ?
Harald
--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
Us
Hi. What does "PGDG" mean, as in PGDG84, the PostgreSQL repository
containing PostgreSQL 8.4.x, etc?
Thanks,
Aleksey
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Dear Steve,
Thanks for your suggestions!
I ended up switching from the Enterprise DB installer to the
Postgres PGDG84 YUM repository, since (a) it provides PostgreSQL 8.4.4
AND Slony 1.x (unlike Enterprise DB installer which only has
Slony 2.0.2 which has a potential data loss problem), and n
2010/6/8 Peter Hunsberger
> On Tue, Jun 8, 2010 at 1:26 PM, uaca man wrote:
> >> 2) Think of the front end as changing states as the user interacts
> >> with it, then figure out what queries need to be made to correspond to
> >> the changes in state. For example, it is unlikely the user needs t
I have several tables with text columns that contain information that
I would like to be able to search using a FTS index. For each text
column, there is also a column that is a foreign key into a language
table for the language used in the text. My idea is to add a column
to the language table t
On 06/04/2010 06:28 PM, Aleksey Tsalolikhin wrote:
Hi.
...
Now we have our first CentOS 5.5 server (64-bit) and I installed
PostgreSQL 8.4.4 using the EnterpriseDB installer, and it is unable to
start the database instance. If I try to start it manually, I get a
Segmentation Fault. I tri
On Tue, Jun 8, 2010 at 5:04 AM, John Gage wrote:
> I do suggest that a plain text file of the entire documentation be made part
> of the documentation armamentarium.
Not that I see a whole lot of utility in this endeavor, but it's
possible to do a decent PDF to plain text conversion. I tried some
On 6/8/10 2:03 PM, "Alvaro Herrera" wrote:
>
> I've seen this problem (and others) in a high-load environment. Not
> Slony related though.
>
> I wrote a small tool to check btree index files for consistency problems
> such as this one, by parsing pg_filedump output. I've seen strange
> thin
On 6/8/2010 2:08 PM, Aaron Burnett wrote:
thanks very much Andy. Very elegant.
I do need to presere the users that have<5 entries though, so I think I can
modify your function to do that as well.
Thanks again.
Oh, duh! because nothing is less than 1900-01-01... my date math
sucks. It s
On 6/8/2010 11:29 AM, Aaron Burnett wrote:
Greetings,
I hope this is the proper list for this, but I am a loss on how to achieve
one particular set of results.
I have a table which is a list of users who entered a contest. They can
enter as many times as they want, but only 5 will count. So so
On Tue, Jun 8, 2010 at 1:26 PM, uaca man wrote:
>> 2) Think of the front end as changing states as the user interacts
>> with it, then figure out what queries need to be made to correspond to
>> the changes in state. For example, it is unlikely the user needs the
>> amount of "gold" updated every
Excerpts from Jeff Amiel's message of mar jun 08 09:26:25 -0400 2010:
> Not looking for help...just putting some data out there.
>
> 2 previous crashes caused by corrupt slony indexes
>
> http://archives.postgresql.org/pgsql-general/2010-02/msg00022.php
>
> http://archives.postgresql.org/pgsql-g
Excerpts from Jeff Amiel's message of mar jun 08 14:19:02 -0400 2010:
> " It seems preferable to configure autovacuum to avoid vacuum
> Slony-I-managed configuration tables. "
>
>
> HmmmI don't do this.
> Surely this is not relative to my corrupt indexes2 attempted vacuums on
> same inde
On 6/8/2010 1:26 PM, uaca man wrote:
> 2) Think of the front end as changing states as the user interacts
> with it, then figure out what queries need to be made to correspond to
> the changes in state. For example, it is unlikely the user needs the
> amount of "gold" updated every 5 seconds
On 6/8/2010 11:29 AM, Aaron Burnett wrote:
Greetings,
I hope this is the proper list for this, but I am a loss on how to achieve
one particular set of results.
I have a table which is a list of users who entered a contest. They can
enter as many times as they want, but only 5 will count. So so
Justin Graf wrote:
There are linux chm readers
...
Note that even Microsoft deprecated CHM back in 2003 after it was
realized it was full of potential security exploits that couldn't
readily be abated.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chang
> 2) Think of the front end as changing states as the user interacts
> with it, then figure out what queries need to be made to correspond to
> the changes in state. For example, it is unlikely the user needs the
> amount of "gold" updated every 5 seconds. Rather, they need to know
> how much the
On 6/8/10 1:15 PM, "Jaime Casanova" wrote:
> On Tue, Jun 8, 2010 at 12:49 PM, Jeff Amiel wrote:
>>
>> Does Slony manage it's own vacuuming separate from postgres' autovacuum?
>>
>
> Yes it does: http://www.slony.info/documentation/maintenance.html
" It seems preferable to configure aut
On Tue, Jun 8, 2010 at 1:00 PM, uaca man wrote:
> This would work except for one thing, the building may affect another
> buildings, Consider this:
>
> the user starts one construction that will finish in 10 minutes and the
> building will give a bonus of +5 gold each seconds for the user. This ha
On Tue, Jun 8, 2010 at 12:49 PM, Jeff Amiel wrote:
>
> Does Slony manage it's own vacuuming separate from postgres' autovacuum?
>
Yes it does: http://www.slony.info/documentation/maintenance.html
--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL
--
Sent vi
2010/6/8 Kalai R
> Sir,
>
> I am using the following psql query with union and subqueries in my
> project.
>
>
> select a.areaname,f.fmno,fm.mno,f.aliasno as falias,f.salutation as
> fsal,f.headname, fm.aliasno as fmalias,fm.salutation as fmsal,fm.membername,
> extract (year from age(now(), to_da
Sir,
I am using the following psql query with union and subqueries in my project.
select a.areaname,f.fmno,fm.mno,f.aliasno as falias,f.salutation as
fsal,f.headname, fm.aliasno as fmalias,fm.salutation as fmsal,fm.membername,
extract (year from age(now(), to_date(fm.dob,'-MM-dd'))) as age,
On 6/8/10 12:56 PM, "Tom Lane" wrote:
> Jeff Amiel writes:
>> On a side note, I am 100% sure that autovacuum was disabled when I brought
>> the database back up after the core dump(s). However, minutes after
>> restarting, some of my larger tables started getting vacuumed by pgsql user.
>> A
>You should investigate a proper queueing or job scheduling solution,
>such as RabbitMQ or Qpid or gearman. They are designed for this type
>of requirement.
All of those(RabbitMQ , Qpid and gearman) are messages queue and are used to
exchange message between different process, system, application
This would work except for one thing, the building may affect another
buildings, Consider this:
the user starts one construction that will finish in 10 minutes and the
building will give a bonus of +5 gold each seconds for the user. This has to
be available in the seconds that the build is done an
Jeff Amiel writes:
> On a side note, I am 100% sure that autovacuum was disabled when I brought
> the database back up after the core dump(s). However, minutes after
> restarting, some of my larger tables started getting vacuumed by pgsql user.
> Any way that a vacuum would kick off for a particu
On 6/8/2010 11:29 AM, Aaron Burnett wrote:
Greetings,
I hope this is the proper list for this, but I am a loss on how to achieve
one particular set of results.
I have a table which is a list of users who entered a contest. They can
enter as many times as they want, but only 5 will count. So so
Thank you very much, Mike!
We'll have a look at that.
On Tue, Jun 8, 2010 at 00:03, Mike Christensen wrote:
> Ok I did more investigation on this and traced the issue down to a
> singe npgsql bug. Enums actually work fine, as long as you're using
> an IDataReader to get at the data. Once you
On 6/8/10 11:23 AM, "Tom Lane" wrote:
> In your original report you mentioned that the next autovacuum attempt
> on the same table succeeded without incident. Has that been true each
> time? I wonder whether this is some transient state, rather than actual
> corruption that you need to REINDEX
Hello my fellow postgreSQL gurus. I´m a user of postgresSQL of quite some
time now, but most of my experience is consuming database, and for the
current project we are without a proper DBA and they have to bear with me
and so I must seek advice.
I have a list of building and a queue and the user
On 6/8/2010 11:53 AM, uaca man wrote:
Hello my fellow postgreSQL gurus. I´m a user of postgresSQL of quite
some time now, but most of my experience is consuming database, and for
the current project we are without a proper DBA and they have to bear
with me and so I must seek advice.
I have a lis
***SNIP***
> 2) Its also available in chm windows help file format. Which i find
> allot
> more useful
> http://www.postgresql.org/docs/manuals/
> you could print chm to a text file.
>
> --I'll have to boot over to XP, ugh. Will do.
There are linux chm readers
http://www.linux.com/news/sof
On Tue, Jun 8, 2010 at 12:53 PM, uaca man wrote:
> Lets say for a 20 thousand users server, it may have at most 20 thousand
> constructions started at the same time.
>
> To accomplish such behavior so far I could come up with two options:
>
> 1. Make a never ending function that will look at
jus...@magwerks.com (Justin Graf) writes:
> Its also available in chm windows help file format. Which i find allot
> more useful
> http://www.postgresql.org/docs/manuals/
> you could print chm to a text file.
>
> also it not hard to dump a PDF document into a text file.
I wish I could find a co
Hello my fellow postgreSQL gurus. I´m a user of postgresSQL of quite some
time now, but most of my experience is consuming database, and for the
current project we are without a proper DBA and they have to bear with me
and so I must seek advice.
I have a list of building and a queue and the user
Thank you all for your suggestions. Thank you very much.
John
1) I suppose the next thing you'll be suggesting is that, because
Postgres is a database, the documentation should be stored as some
form of searchable table within the database itself?
--Well, that is exactly what I have
Greetings,
I hope this is the proper list for this, but I am a loss on how to achieve
one particular set of results.
I have a table which is a list of users who entered a contest. They can
enter as many times as they want, but only 5 will count. So some users have
one entry, some have as many as
Jeff Amiel writes:
> New one yesterday.
> Jun 7 15:05:01 db-1 postgres[9334]: [ID 748848 local0.crit] [3989781-1]
> 2010-06-07 15:05:01.087 CDT9334PANIC: right sibling 169 of block 168 is
> not next child of 249 in index "sl_seqlog_idx"
In your original report you mentioned that the next
Hi Greg,
first of all thank you for your answer below.
The first problem of the query performing slowly has been solved with a
FULL VACUUMING of the database.
Now the problem of the sequence remains.
This e-mail is sent to pgsql-general@postgresql.org e-mail address too, as
per your suggestion
On 6/8/10 10:47 AM, "Stephen Frost" wrote:
> Then you've been through this before.. Perhaps you should go check out
> what you did then. Back before 8.1, we didn't use OIDs for
> users/groups. :) Changing to OIDs was part of the work that I did to
> add role support.
Hmmm...this code has b
* Jeff Amiel (jam...@istreamimaging.com) wrote:
> On 6/8/10 10:39 AM, "Stephen Frost" wrote:
> > I'm afriad you're not going to have a choice.. I would recommend
> > creating a mapping from the old IDs to the new ones as part of this
> > upgrade, to keep the historical information. Guess it's no
On 6/8/10 10:39 AM, "Stephen Frost" wrote:
> I'm afriad you're not going to have a choice.. I would recommend
> creating a mapping from the old IDs to the new ones as part of this
> upgrade, to keep the historical information. Guess it's not nice to
> point this out- but you really shouldn't h
* Jeff Amiel (jam...@istreamimaging.com) wrote:
> On 6/8/10 10:30 AM, "Thom Brown" wrote:
> > Can't you switch to using role names? I don't think oids are intended
> > to be used by anything other than PostgreSQL.
>
> :( If only I couldmassive audit tables contain these IDs with years of
> d
On 6/8/10 10:30 AM, "Thom Brown" wrote:
> Can't you switch to using role names? I don't think oids are intended
> to be used by anything other than PostgreSQL.
:( If only I couldmassive audit tables contain these IDs with years of
data
We have a plan to change to sequence values store
On 8 June 2010 15:59, Jeff Amiel wrote:
> We currently use the 'usesysid' column from pg_shadow (which is really
> pg_authid.oid I assume) for a trigger-based auditing mechanism.
>
> We are about to do a dump from an 8.2 database into 8.4 and would like to
> preserve the usesysid/oid when restorin
We currently use the 'usesysid' column from pg_shadow (which is really
pg_authid.oid I assume) for a trigger-based auditing mechanism.
We are about to do a dump from an 8.2 database into 8.4 and would like to
preserve the usesysid/oid when restoring.
No matter what options I throw ad pg_dumpall,
On Tue, Jun 8, 2010 at 9:26 AM, Jeff Amiel wrote:
> That being said, the fact that each time this has happened, it has been a
> slony index that has been corrupt, I find it 'odd'. While I can't imagine a
> bug in slony corrupting postgres indexes...and I can't imagine a bug in
> postgres corru
* John Gage (jsmg...@numericable.fr) wrote:
> But either I am a visitor from the Crab Nebula, or there is someone else
> out there who would like to have a text file of the entire
> documentation.
Soo.. there are quite a few man pages, and in-psql's help is also
pretty nice (\h and \?). That
On 6/8/2010 9:23 AM, Peter Hunsberger wrote:
> On Tue, Jun 8, 2010 at 4:04 AM, John Gage wrote:
>
>> Unix is a text-based operating system with unbelievably helpful text
>> manipulation tools.
>>
>> Postgres is a creature of Unix which happens to have unbelievable text
>> searching and manipul
On Tue, Jun 8, 2010 at 4:04 AM, John Gage wrote:
> Unix is a text-based operating system with unbelievably helpful text
> manipulation tools.
>
> Postgres is a creature of Unix which happens to have unbelievable text
> searching and manipulation tools.
>
> Yet, the only one file edition of the Pos
John Gage wrote:
I also use the National Library of Medicine's MeSH subject headings.
25,000 descriptors with definitions, synonyms and a lot of other things.
They give it to you in single files either as text, xml, or other ways.
Big files. Hundreds of megabytes. That makes it so that you can do
Hi
All,
We are getting following error on intermittent basis when we write data into
database. We are on postgreSQL
8.0.2, with slony I. We used to stop the replication, taking back-up from the
primary, restore it on secondary server and again start the replication again.
We
used to do above ac
Not looking for help...just putting some data out there.
2 previous crashes caused by corrupt slony indexes
http://archives.postgresql.org/pgsql-general/2010-02/msg00022.php
http://archives.postgresql.org/pgsql-general/2009-12/msg01172.php
New one yesterday.
Jun 7 15:05:01 db-1 postgres[9334]
On 8/06/2010 8:25 PM, Jaiswal Dhaval Sudhirkumar wrote:
Hi All,
We are getting following error on intermittent basis when we write data
into database. We are on postgreSQL 8.0.2
While this doesn't help you track down your problem directly ... 8.0.2?
Really? Version 8.0 is up to patch level 25
On Tue, 08 Jun 2010 10:25:49 +0800, Craig Ringer wrote:
>On 8/06/2010 9:11 AM, John T. Dow wrote:
>> OP here
>>
>> We removed AVG from the computer and rebooted.
>>
>> Same problem.
>
>OK, good to know. Thanks very much for testing that, and my apologies
>for recommending something that didn'
Hi All,
We are getting following error on intermittent basis when we write data
into database. We are on postgreSQL 8.0.2, with slony I. We used to stop
the replication, taking back-up from the primary, restore it on
secondary server and again start the replication again. We used to do
above acti
On Thu, Jun 3, 2010 at 9:22 AM, Max Williams wrote:
> Hi,
>
> I was doing some benchmarking while changing configuration options to try to
> get more performance out of our postgresql servers and noticed that when
> running pgbench against 8.4.3 vs 8.4.4 on identical hardware and
> configuration t
Unix is a text-based operating system with unbelievably helpful text
manipulation tools.
Postgres is a creature of Unix which happens to have unbelievable text
searching and manipulation tools.
Yet, the only one file edition of the Postgres documentation is
in...pdf format. Huh?
I know
On 8 June 2010 03:02, Mike Toews wrote:
> Hi,
>
> I have a question that is not specified in the docs[1]. I am using
> deferrable constraints in a transaction with SET CONSTRAINTS ALL
> DEFERRED. Now I know that DEFERRED constraints are not checked until
> transaction COMMIT (i.e., the end), howev
63 matches
Mail list logo
