Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Manuel Sugawara wrote:
>
>> A friend is doing the queries right now but it takes time :-(, mean
>> time I was wondering if it will be safe to apply the following patch
>> just to get the database up and be able to run pg_dumpall:
>
> Yes, it is safe. J
Manuel Sugawara wrote:
> A friend is doing the queries right now but it takes time :-(, mean
> time I was wondering if it will be safe to apply the following patch
> just to get the database up and be able to run pg_dumpall:
Yes, it is safe. Just make sure to get a copy of the database out in
50
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Manuel Sugawara wrote:
>> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>>
>> > Hmm, nope -- take away the relnamespace check, because there is a
>> > different namespace for each backend (pg_temp_2, pg_temp_3, etc).
>>
>> Still no luck, changed the qu
imageguy <[EMAIL PROTECTED]> writes:
> On Apr 8, 12:20 pm, [EMAIL PROTECTED] (Tom Lane) wrote:
>> It was raised to 100 in 8.1.
> Thanks Tom.
> - forgive me for asking but where would I find this in the docs ?
Under the max_function_args parameter, or in the 8.1 release notes ...
Jeff Amiel <[EMAIL PROTECTED]> writes:
> Sure enough...I put a #ERROR at the top of the 'old/incorrect' ssl..h and
> did a make clean/make and errored out.
> So I was building with 0.9.8 libraries...but 0.9.7 header files.
Fascinating. I read your previous mail and was about to reply that
/usr/l
Manuel Sugawara wrote:
Going back to your first message I see that I missed something
important:
> 1: relname = "pg_tablespace" (typeid = 19, len = 64, typmod = -1, byval = f)
> 2: age = "2146484675" (typeid = 23, len = 4, typmod = -1, byval = t)
> 1: relname = "pg_pltemplate" (typeid = 19, le
Manuel Sugawara wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>
> > Hmm, nope -- take away the relnamespace check, because there is a
> > different namespace for each backend (pg_temp_2, pg_temp_3, etc).
>
> Still no luck, changed the query to:
>
> select relname, age(relfrozenxid) fro
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Hmm, nope -- take away the relnamespace check, because there is a
> different namespace for each backend (pg_temp_2, pg_temp_3, etc).
Still no luck, changed the query to:
select relname, age(relfrozenxid) from pg_class join pg_namespace n on (n.oi
Tom Lane wrote:
One idea: you are linking to /usr/local/ssl/lib/libssl.so, but is
it possible that when you compile PG it is finding the header files
for some other version?
Sure
enough...I put a #ERROR at the top of the 'old/incorrect' ssl..h and
did a make clean/make and errored out.
So
Tom Lane wrote:
One idea: you are linking to /usr/local/ssl/lib/libssl.so, but is
it possible that when you compile PG it is finding the header files
for some other version?
yes...if I could figure out how the include path is being set on the
postgresql build.
I'm looking at the config.log
Jeff Amiel <[EMAIL PROTECTED]> writes:
> Now their are 2 subscriber nodes that connect to this node for slony
> replication...
> One is running the same version (libssl 0.9.8e) but one is running
> 0.9.7e-p1 2.
> could this be an issue?
Seems unlikely, that would mean that openssl failed to pre
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Hmm, nope -- take away the relnamespace check, because there is a
> different namespace for each backend (pg_temp_2, pg_temp_3, etc). And
> as far as I've seen, most leftover temp tables are on "high" temp
> schemas (i.e. those belonging to backends tha
On Apr 8, 12:20 pm, [EMAIL PROTECTED] (Tom Lane) wrote:
> Richard Huxton <[EMAIL PROTECTED]> writes:
> > imageguy wrote:
> >> I am attempting to port and application that was designed for MS-SQL
> >> to Postgres and bumped into a limitation of pg functions, namely that
> >> pg functions can only su
Jeff Amiel wrote:
Now their are 2 subscriber nodes that connect to this node for slony
replication...
One is running the same version (libssl 0.9.8e) but one is running
0.9.7e-p1 2.
could this be an issue?
Note that both nodes are set to 'hostnossl' in the pg_hba.conf
--
Sent via pgsql-g
Tom Lane wrote:
The previous thread suggested that you might have a problem with
different bits of code being linked to different versions of libssl.
Did you ever resolve that? Given the lack of other reports, I'm
pretty suspicious that it's something like that, rather than a real
bug in either
Manuel Sugawara wrote:
> In each database executed:
>
> select relname, age(relfrozenxid) from pg_class where relnamespace =
> '10406'::oid;
>
> (note that 10406 is the oid of the pg_temp_1 namespace) none of them
> showed temp tables, Is this the correct way?, Any other idea?.
Hmm, nope --
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Manuel Sugawara wrote:
>
> Hi Manuel,
>
>> The funny thing is that there was no open transactions, even after
>> restarting the cluster the same message was logged. Today, the
>> database stopped working as expected:
>>
>> ERROR: database is shut down
Jeff Amiel wrote:
> Stack trace looks eerily familiar:
>
> Core was generated by `/usr/local/pgsql/bin/postgres -D /db'.
> Program terminated with signal 11, Segmentation fault.
> #0 0xfee8ec23 in sk_value () from /usr/local/ssl/lib/libcrypto.so.0.9.8
>
> *grumble*
Did you try installing the O
Jeff Amiel <[EMAIL PROTECTED]> writes:
> As the proud author of this previous post:
>
> href="http://archives.postgresql.org/pgsql-general/2007-08/msg01911.php";> class="yshortcuts"
> id="lw_1207670543_0">http://archives.postgresql.org/pgsql-general/2007-08/msg01911.php
(Non-HTML posts are pr
On Tue, Apr 8, 2008 at 9:30 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Mikko Partio" <[EMAIL PROTECTED]> writes:
> > On Tue, Apr 8, 2008 at 6:38 PM, Zdenek Kotala <[EMAIL PROTECTED]>
> wrote:
> >> It is really strange. It would be nice to have reproduce scenario. Can
> you
> >> run same DDL comman
"PostgreSQL 8.2.4 on i386-pc-solaris2.10, compiled by GCC gcc (GCC) 3.4.3
(csl-sol210-3_4-branch+sol_rpath)"
As the proud author of this previous post:
http://archives.postgresql.org/pgsql-general/2007-08/msg01911.php
I never found a real answer except to disable SSL on the connections betwee
"Mikko Partio" <[EMAIL PROTECTED]> writes:
> On Tue, Apr 8, 2008 at 6:38 PM, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
>> It is really strange. It would be nice to have reproduce scenario. Can you
>> run same DDL command which invoke a catalog corruption on test database
>> cluster?
> I tried it on
Gordon wrote:
So what I want to know is, is there a way to tell if executing a query
caused a trigger to fire? I don't need anything fancy like notify
and listen, I just want to see what the database is doing for testing
purposes. For example by looking at the logs and seeing what activity
wa
Richard Huxton wrote:
[EMAIL PROTECTED] wrote:
I am looking now at a scenario that does not seem to be a native
ability of Postgres, but might possibly be overcome with Sequoia. I am
hoping that there exists the possibility of using Sequoia to replicate
a DB between / among a number of machine
I wrote:
> Would you confirm that
> select atttypid from pg_attribute where attrelid =
> 'public.ct_com_board_message'::regclass and attname = 'idxfti';
> gives 3614 (the preassigned OID for pg_catalog.tsvector)?
Actually, I'll bet a nickel that you'll find it doesn't, but rather
returns the OID
On Tue, Apr 8, 2008 at 6:38 PM, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
> Mikko Partio napsal(a):
>
> On Tue, Apr 8, 2008 at 5:26 PM, Mikko Partio <[EMAIL PROTECTED]> wrote:
> >
> > Ok I removed the faulty tuple and nothing catastrophical happened. I
> > > can
> > > do a pg_dump now, but I stil
On Tue, 8 Apr 2008 11:19:57 -0600
Keaton Adams <[EMAIL PROTECTED]> wrote:
> there a way for an object (variable/table/etc) to remain persistent
> in memory that is shared among multiple client sessions? If not, an
> alternative we thought of is to use a small table within the DB in
> conjunction
Just a FYI, you can get around the 32 param limit in older versions of
postgresql by passing the function a varchar/text array, then use the
built in array functions to pull the "params" from the passed array.
Something like this(not tested code, just a sample):
CREATE or REPLACE FUNCTION tes
Is there a way to manage a queue in memory within Postgres?
We have a scenario where we have a list of servers stored in a table. Multiple
clients make a request for the next "group" of servers to process. Something
within the database needs to keep track of the last server set that was passe
"Markus Wollny" <[EMAIL PROTECTED]> writes:
> So everything's working as expected apart from that built-in trigger
> function.
Well, that's just strange. I tried to duplicate your example without
any success (ie, it worked fine) --- although it seemed you hadn't
shown the trigger definition ex
It sounds to me like two possible problems, maybe combined.
One possibility is that you have a data distribution that results in
statistics being gathered that don't really represent your data. Try
increasing the stats target for that column (or the whole db if you'd
rather) and re-running analyz
On Tuesday 08 April 2008, [EMAIL PROTECTED] wrote:
> The problem is that we have peaktimes were everything is running fine. It
> has something to do with the vacuum process running. To simplify my
> problem:
>
> - I run vaccum analyze concurrently with some few user queries: slows
> down to a crawl
Richard Huxton <[EMAIL PROTECTED]> writes:
> imageguy wrote:
>> I am attempting to port and application that was designed for MS-SQL
>> to Postgres and bumped into a limitation of pg functions, namely that
>> pg functions can only support 32 parameters.
> I thought it had been increased to 64, but
HI Richard,
thanks for your immediate response. I will answer your questions below:
Am Dienstag, 8. April 2008 17:40 schrieb Richard Huxton:
> [EMAIL PROTECTED] wrote:
> > We looked in our cpu monitoring and saw that we have huge IOwait while
> > VACUUM is running, not unusual though. But just af
Volkan YAZICI escreveu:
Mike Ginsburg <[EMAIL PROTECTED]> writes:
There is probably a really simple solution for this problem, but for
the life of me I can't see to think of it. I have three tables
--contains u/p for all users in the site
TABLE users (user_id INT primary key, username VARCHAR(
[EMAIL PROTECTED] wrote:
Hi Guys,
I have been testing / working with Postgres for a work project, and so
far I am really impressed with this DB system. Takes a little getting
used to, but I am really beginning to love it.
Good to hear it Mr ...Umm... Frog.
I am looking now at a scenario that
Kev wrote:
Recompile PG? Even if I'm running 8.3.1, released well after that?
Oh, sorry, do you mean, it's ready for 5.10 but still compiled with
5.8 for now? If so, is there a timeline for compiling with 5.10 by
default in the production releases of pgsql?
Like Alvaro says, that will be do
imageguy wrote:
I am attempting to port and application that was designed for MS-SQL
to Postgres and bumped into a limitation of pg functions, namely that
pg functions can only support 32 parameters.
I thought it had been increased to 64, but I'm sure you're right.
Our app takes records from
[EMAIL PROTECTED] wrote:
We looked in our cpu monitoring and saw that we have huge IOwait while VACUUM
is running, not unusual though. But just after VACUUM was finished, the
userCPU load raised to 200% (dual cpu). At this time in the early morning
there were only very few users using our app.
Mikko Partio napsal(a):
On Tue, Apr 8, 2008 at 5:26 PM, Mikko Partio <[EMAIL PROTECTED]> wrote:
Ok I removed the faulty tuple and nothing catastrophical happened. I can
do a pg_dump now, but I still can't remove the one remaining table:
# drop table xyz ;
ERROR: too many trigger records found
I am attempting to port and application that was designed for MS-SQL
to Postgres and bumped into a limitation of pg functions, namely that
pg functions can only support 32 parameters.
Our app takes records from a only cobol file(s) and populates an SQL
table(s), such that one table in the db = one
Gordon wrote:
I'm adding full text search to a CMS project after we upgraded to 8.3
of Postgres. I'd like to do a bit of testing before deploying it.
I added columns to the pertinent tables for storing tsvectors, and was
looking at my query code to update it so these columns get updated
where a
Hi all,
our postgresql DB was running fine for a long time, but suddenly we
encountered a huge problem which we got fixed only temporarily.
We are running debian stable with postgresql 8.1.11. Our app is connecting via
JDBC and uses Prepared Statements.
We are not running autovacuum but a nig
Kev escribió:
> > Recompile PG? Even if I'm running 8.3.1, released well after that?
>
> Oh, sorry, do you mean, it's ready for 5.10 but still compiled with
> 5.8 for now? If so, is there a timeline for compiling with 5.10 by
> default in the production releases of pgsql?
You should request tha
On Tue, Apr 08, 2008 at 07:03:07AM -0700, Gordon wrote:
> But I do have one concern regarding performance. The tsvector only
> needs to be updated if the title, summary, or keywords fields have
> changed. If they are the same after an update then there is no need
> to run them. Doing so would on
> Recompile PG? Even if I'm running 8.3.1, released well after that?
>
> Thanks,
> Kev
Oh, sorry, do you mean, it's ready for 5.10 but still compiled with
5.8 for now? If so, is there a timeline for compiling with 5.10 by
default in the production releases of pgsql?
Thanks,
Kev
--
Sent via pg
I'm adding full text search to a CMS project after we upgraded to 8.3
of Postgres. I'd like to do a bit of testing before deploying it.
I added columns to the pertinent tables for storing tsvectors, and was
looking at my query code to update it so these columns get updated
where appropriate when
On Apr 8, 4:07 pm, [EMAIL PROTECTED] ("Harald Armin Massa")
wrote:
> Simone,
>
> one of the main European Python Events will be:
>
> EuroPython 2008 in Vilnius, Lithuania
> Monday 7th July - Saturday 12th July at the Reval Hotel Lietuva
>
> > do you know of any interesting Postgresql Conferences
paul tilles <[EMAIL PROTECTED]> writes:
> {
> timestamp dt1st, dt2nd;
> interval *int_day, *int_pt;
> char timebeg[40];
> char timeend[40];
> int rc;
> strcpy(timebeg,"2008-04-01");
> strcpy(timeend,"2008-04-05");
> printf("timebeg: %s\n", timebeg);
> printf("timeend: %s\n", timeend);
A colleague of mine is working with the following code (postgres Version
8.2.4):
#include
#include
#include "pgtypes_timestamp.h"
#include "pgtypes_interval.h"
EXEC SQL INCLUDE sqlca;
main(argc, argv)
int argc;
char *argv[];
{
timestamp dt1st, dt2nd;
interval *int_day, *int_pt;
char tim
On Tue, Apr 8, 2008 at 5:26 PM, Mikko Partio <[EMAIL PROTECTED]> wrote:
>
> Ok I removed the faulty tuple and nothing catastrophical happened. I can
> do a pg_dump now, but I still can't remove the one remaining table:
>
> # drop table xyz ;
> ERROR: too many trigger records found for relation "x
On Tue, Apr 8, 2008 at 1:45 PM, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
> Mikko Partio napsal(a):
>
> Should I try remove one of the duplicate rows from pg_class?
> >
>
> Try it with caution. You should use ctid column to refer to exact row.
>
>
Ok I removed the faulty tuple and nothing catastr
On Tue, Apr 08, 2008 at 02:39:32PM +0300, Sim Zacks wrote:
> Is there any way to do a dirty select to find out what a process is up
> to?
No.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-gen
Simone,
one of the main European Python Events will be:
EuroPython 2008 in Vilnius, Lithuania
Monday 7th July - Saturday 12th July at the Reval Hotel Lietuva
> do you know of any interesting Postgresql Conferences/events in Europe
> in 2008? Or PHP/Python events as well?
Quite likely ther
Simone Brunozzi wrote:
> Greetings, guys,
> do you know of any interesting Postgresql Conferences/events in Europe
> in 2008? Or PHP/Python events as well?
There will be a pgDay in Italy in october (www.pgday.it), and IIRC
there is also a pgDay or so coming up in France, but I don't think
they've
Hi Guys,
I have been testing / working with Postgres for a work project, and so
far I am really impressed with this DB system. Takes a little getting
used to, but I am really beginning to love it.
I am looking now at a scenario that does not seem to be a native
ability of Postgres, but might poss
On Tue, Apr 08, 2008 at 03:44:47PM +0200, Giorgio Valoti wrote:
> Hi all, the documentation says that functions are always executed
> within the transaction established by the outer query. However, I was
> quite surprised (in a positive way, that is) seeing that if a
> function call cau
Greetings, guys,
do you know of any interesting Postgresql Conferences/events in Europe
in 2008? Or PHP/Python events as well?
Thanks
Simone Brunozzi
www.ubuntista.it
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresq
"Hardwick, Joe" <[EMAIL PROTECTED]> writes:
> I've got a Postgres v8.2.4 server that we recently upped from 2GB RAM to
> 6GB. I added:
> effective_cache_size = 5120MB
> to the postgresql.conf file but when I restart the server and do a "show
> all" it always comes back with "1000MB". I can set
Mikko Partio napsal(a):
How can I tell if there is clog corruption?
Unfortunatelly, I'm afraid that there is not way how to check it. CLOG file is
only array of bits and it does not contains any CRC or backup copy. Try to check
filesystem integrity.
Zdenek
--
Sent via pgsql-gene
On Apr 7, 10:37 am, [EMAIL PROTECTED] (Tom Lane) wrote:
> Kev <[EMAIL PROTECTED]> writes:
> > I'm trying to upgrade to perl 5.10, and realized that plperlu is still
> > using 5.8. How exactly does pgsql determine where to look/what
> > version to use for plperlu?
>
> You need to recompile. You al
> > Anyway, you can use `psql' to query the activity tables using something
> > like "SELECT procpid FROM pg_stat_activity WHERE datname = 'dbtodrop'"
> > and see which backend pids need to be killed, then use 'pg_ctl kill
> > signame pid' to kill them. A bit of powershell, cmd.exe, etc should do
>
Hi all, the documentation says that functions are always executed
within the transaction established by the outer query. However, I was
quite surprised (in a positive way, that is) seeing that if a
function call causes some error, the whole function is "rolled back".
Is this the expected b
"You should probably send those logs to the list, rather than straight to
me.
However, this line sticks out at me:
2008-04-07 07:43:14 GMT FATAL: lock file "postmaster.pid" already exists
2008-04-07 07:43:14 GMT HINT: Is another postmaster (PID 3724) running
in data directory "F:/B"?
Is it
Volkan,
> CREATE SEQUENCE document_docorder_seq START 1;
>
> UPDATE document
> SET docorder = T.docorder
> FROM (SELECT nextval('document_docorder_seq') AS docorder, docdate
> FROM document
> ORDER BY docdate) AS T
> WHERE document.docdate = T.docdate;
>
> DROP SEQUENCE documen
I've got a Postgres v8.2.4 server that we recently upped from 2GB RAM to
6GB. I added:
effective_cache_size = 5120MB
to the postgresql.conf file but when I restart the server and do a "show
all" it always comes back with "1000MB". I can set it manually and it
takes but for some reason it just s
On Tue, Apr 8, 2008 at 2:49 PM, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
> Mikko Partio napsal(a):
>
> On Tue, Apr 8, 2008 at 1:45 PM, Zdenek Kotala <[EMAIL PROTECTED]>
> > wrote:
> >
> > Mikko Partio napsal(a):
> > >
> > > Should I try remove one of the duplicate rows from pg_class?
> > > Try
> -Mensaje original-
> De: Tom Lane [mailto:[EMAIL PROTECTED]
> Enviado el: Lunes, 07 de Abril de 2008 01:37
> Para: Fernando Hevia
> CC: pgsql-general@postgresql.org
> Asunto: Re: [GENERAL] Removing Context messages
>
> "Fernando Hevia" <[EMAIL PROTECTED]> writes:
> > I want to get rid
Gregory Stark escribió:
> I thought our DISTINCT index scan does do that but it still has to read the
> index leaf pages sequentially. It doesn't back-track up the tree structure and
> refind the next key.
The way to back-track is to start the scan over from the root page down,
keeping a stack of
Is there any way to do a dirty select to find out what a process is up
to? I have a process that is writing 150,000 rows to a table and it is
taking way longer then I thought it would. I would like to read the
table to make sure that it is not looping through the data or anything
like that.
Thank
Mikko Partio napsal(a):
On Tue, Apr 8, 2008 at 1:45 PM, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
Mikko Partio napsal(a):
Should I try remove one of the duplicate rows from pg_class?
Try it with caution. You should use ctid column to refer to exact row.
Try before:
select oid, ctid, xmin, xm
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> Tom Lane escribió:
>>> What I think you'll find, though, is that once you do force an indexscan
>>> to be picked it'll be slower. Full-table index scans are typically
>>> worse than seqscan+sort, unintuitive th
On Tue, Apr 8, 2008 at 1:45 PM, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
> Mikko Partio napsal(a):
>
> Should I try remove one of the duplicate rows from pg_class?
> >
>
> Try it with caution. You should use ctid column to refer to exact row.
>
> Try before:
>
> select oid, ctid, xmin, xmax, cmin
Mikko Partio napsal(a):
Should I try remove one of the duplicate rows from pg_class?
Try it with caution. You should use ctid column to refer to exact row.
Try before:
select oid, ctid, xmin, xmax, cmin, cmax, relname from pg_class where oid =
294397;
If both row are identical or not.
On Tue, Apr 8, 2008 at 1:19 PM, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
> Mikko Partio napsal(a):
>
> >
> >
> > I little investigation showed that there is duplicate row in pg_class:
> >
> > # select oid from pg_class group by oid having count(*) > 1 ;
> > oid
> >
> > 294397
> > (1 row
Mikko Partio napsal(a):
I little investigation showed that there is duplicate row in pg_class:
# select oid from pg_class group by oid having count(*) > 1 ;
oid
294397
(1 row)
Could you check if pg_attribute is doubled for this relation?
Zdenek
--
Sent via pgsql
On Tue, Apr 8, 2008 at 12:20 PM, Mikko Partio <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, Apr 8, 2008 at 11:27 AM, Zdenek Kotala <[EMAIL PROTECTED]>
> wrote:
>
> >
> >
> > Mikko Partio napsal(a):
> >
> > > Hello all
> > >
> > > Postgres version 8.3.1
> > >
> > > I just created a bunch of tables (~10)
On Tue, Apr 8, 2008 at 11:27 AM, Zdenek Kotala <[EMAIL PROTECTED]>
wrote:
>
>
> Mikko Partio napsal(a):
>
> > Hello all
> >
> > Postgres version 8.3.1
> >
> > I just created a bunch of tables (~10) with identical structure; all
> > tables
> > have 6 foreign key references to other tables and a pri
Mikko Partio napsal(a):
Hello all
Postgres version 8.3.1
I just created a bunch of tables (~10) with identical structure; all tables
have 6 foreign key references to other tables and a primary key. To my
surprise, some of the tables were created ok, some missed primary key and
some didn't get
On Mon, Apr 7, 2008 at 9:11 PM, Stephen Denne
<[EMAIL PROTECTED]> wrote:
>
> You may be able to make use of an index by rearranging your query to
> generate a series between your min & max values, testing whether each value
> is in your table.
>
> You've got 4252 distinct values, but what is th
Hello all
Postgres version 8.3.1
I just created a bunch of tables (~10) with identical structure; all tables
have 6 foreign key references to other tables and a primary key. To my
surprise, some of the tables were created ok, some missed primary key and
some didn't get created at all.
Postgres c
81 matches
Mail list logo
