Re: [pgsql-www] Community instance of PentaBarf?

Ciao Josh,

2008/6/18 Josh Berkus <josh@agliodbs.com>:

Pentabarf is the software which we used to schedule and book all three
Canada conferences (Anniversary, pgCon1 and 2).  It's the most
full-featured conference presentation management package available in OSS.

Yes ... and a very hard one to install and configure. :)

I'd like us to have an instance of PB installed on a community server so we
can use it for pgDays and the like. Right now Selena is trying to hack up
something in Drupal and it'll take a lot of work.  PB is Rails, so it's a
bit of a resource hog, but does run on Postgres.  Can we do this?

This is something that we really need. This would speed up the organisation process for PG conferences worldwide, and also speed up the registration process, as speakers information will be shared among events.

As Magnus later pointed out, we were just about to raise the issue again for PGDay EU/IT.

Thanks,
Gabriele

Re: [SQL] order by when using cursors

2008/6/18 Pavel Stehule <pavel.stehule@gmail.com>:
> Hello
>
> it's known problem - column and variable names collision, so when you
> use any SQL statement inside procedure you have to be carefully about
> using variable names.
>
> postgres=# CREATE OR REPLACE FUNCTION testcur( OUT _a integer, OUT _b integer )
> RETURNS SETOF RECORD AS $$
> DECLARE
> cur refcursor;
> BEGIN
> OPEN cur FOR SELECT * FROM ta ORDER BY a DESC;
> LOOP
> FETCH cur INTO _a, _b;
> IF not found THEN
> exit;
> ELSE
> RETURN NEXT;
> END IF;
> END LOOP;
> CLOSE cur;
> END;
> $$ LANGUAGE 'PLPGSQL' ;
>

one note: when you unlike prefixes in result, you can use in ORDER BY
expression ordinal number of an output column, in this case

postgres=# CREATE OR REPLACE FUNCTION testcur( OUT a integer, OUT b integer )
RETURNS SETOF RECORD AS $$
DECLARE
cur refcursor;
BEGIN
OPEN cur FOR SELECT * FROM ta ORDER BY 1 DESC;
LOOP
FETCH cur INTO a, b;
IF not found THEN
exit;
ELSE
RETURN NEXT;
END IF;
END LOOP;
CLOSE cur;
END;
$$ LANGUAGE 'PLPGSQL' ;

other solution is using qualified names everywhere:

CREATE OR REPLACE FUNCTION testcur( OUT a integer, OUT b integer )
RETURNS SETOF RECORD AS $$
DECLARE
cur refcursor;
BEGIN
OPEN cur FOR SELECT ta.a, ta.b FROM ta ORDER BY ta.a DESC; --
ta.a qualified name
LOOP
FETCH cur INTO a, b;
IF not found THEN
exit;
ELSE
RETURN NEXT;
END IF;
END LOOP;
CLOSE cur;
END;
$$ LANGUAGE 'PLPGSQL' ;

Pavel

>
> postgres=# select *from testcur();
> _a | _b
> ----+----
> 4 | 3
> 3 | 1
> 2 | 4
> 1 | 2
> (4 rows)
>
> postgres=#
>
> Regards
> Pavel Stehule
>
>
> 2008/6/18 Patrick Scharrenberg <pittipatti@web.de>:
>> Hi!
>>
>> I did some experiments with cursors and found that my data doesn't get
>> sorted by the "order by"-statement.
>>
>> Here is what I did:
>>
>> ----------------
>>
>> CREATE TABLE ta (
>> a integer NOT NULL,
>> b integer NOT NULL
>> );
>>
>> insert into ta values(3,1);
>> insert into ta values(1,2);
>> insert into ta values(4,3);
>> insert into ta values(2,4);
>>
>> CREATE OR REPLACE FUNCTION testcur( OUT a integer, OUT b integer )
>> RETURNS SETOF RECORD AS $$
>> DECLARE
>> cur refcursor;
>> BEGIN
>> OPEN cur FOR SELECT * FROM ta ORDER BY a DESC;
>> LOOP
>> FETCH cur INTO a,b;
>> IF not found THEN
>> exit;
>> ELSE
>> RETURN NEXT;
>> END IF;
>> END LOOP;
>> CLOSE cur;
>> END;
>> $$ LANGUAGE 'PLPGSQL' ;
>>
>> SELECT * FROM testcur();
>>
>> ----------------
>>
>> As the result I get:
>>
>> 3 1
>> 1 2
>> 4 3
>> 2 4
>>
>>
>> Which is not ordered by column a!?
>>
>> Is this intended?
>> Am I doing something wrong?
>>
>> I'm using Postgresql 8.3.1
>>
>> Patrick
>>
>>
>> --
>> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-sql
>>
>

--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql

Re: [SQL] order by when using cursors

Hello

it's known problem - column and variable names collision, so when you
use any SQL statement inside procedure you have to be carefully about
using variable names.

postgres=# CREATE OR REPLACE FUNCTION testcur( OUT _a integer, OUT _b integer )
RETURNS SETOF RECORD AS $$
DECLARE
cur refcursor;
BEGIN
OPEN cur FOR SELECT * FROM ta ORDER BY a DESC;
LOOP
FETCH cur INTO _a, _b;
IF not found THEN
exit;
ELSE
RETURN NEXT;
END IF;
END LOOP;
CLOSE cur;
END;
$$ LANGUAGE 'PLPGSQL' ;

postgres=# select *from testcur();
_a | _b
----+----
4 | 3
3 | 1
2 | 4
1 | 2
(4 rows)

postgres=#

Regards
Pavel Stehule

2008/6/18 Patrick Scharrenberg <pittipatti@web.de>:
> Hi!
>
> I did some experiments with cursors and found that my data doesn't get
> sorted by the "order by"-statement.
>
> Here is what I did:
>
> ----------------
>
> CREATE TABLE ta (
> a integer NOT NULL,
> b integer NOT NULL
> );
>
> insert into ta values(3,1);
> insert into ta values(1,2);
> insert into ta values(4,3);
> insert into ta values(2,4);
>
> CREATE OR REPLACE FUNCTION testcur( OUT a integer, OUT b integer )
> RETURNS SETOF RECORD AS $$
> DECLARE
> cur refcursor;
> BEGIN
> OPEN cur FOR SELECT * FROM ta ORDER BY a DESC;
> LOOP
> FETCH cur INTO a,b;
> IF not found THEN
> exit;
> ELSE
> RETURN NEXT;
> END IF;
> END LOOP;
> CLOSE cur;
> END;
> $$ LANGUAGE 'PLPGSQL' ;
>
> SELECT * FROM testcur();
>
> ----------------
>
> As the result I get:
>
> 3 1
> 1 2
> 4 3
> 2 4
>
>
> Which is not ordered by column a!?
>
> Is this intended?
> Am I doing something wrong?
>
> I'm using Postgresql 8.3.1
>
> Patrick
>
>
> --
> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-sql
>

--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql

Re: [pgsql-www] Community instance of PentaBarf?

> WWW Team,
>
> Pentabarf is the software which we used to schedule and book all three
> Canada conferences (Anniversary, pgCon1 and 2). It's the most
> full-featured conference presentation management package available in OSS.
>
> I'd like us to have an instance of PB installed on a community server so we
> can use it for pgDays and the like. Right now Selena is trying to hack up
> something in Drupal and it'll take a lot of work. PB is Rails, so it's a
> bit of a resource hog, but does run on Postgres. Can we do this?

I have been looking into doing this for the eu group. Previously the conferences have all made a point of doing their own stuff and not within the web community, but if that has changed lll be happy to make it a general community resource.

/Magnus

--
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www

Re: [GENERAL] UTF8 encoding problem

On Wednesday 18 June 2008 02:04, Michael Fuhr wrote:
> On Tue, Jun 17, 2008 at 10:48:34PM +0100, Garry Saddington wrote:
> > I am getting illegal UTF8 encoding errors and I have traced it to the £
> > sign.
>
> What's the exact error message?
>
> > I have set lc_monetary to "lc_monetary = 'en_GB.UTF-8'" in
> > postgresql.conf but this has no effect. How can I sort this problem?
> > Client_encoding =UTF8.
>
> Is the data UTF-8? If the error is 'invalid byte sequence for encoding
> "UTF8": 0xa3' then you probably need to set client_encoding to latin1,
> latin9, or win1252.
>
Thanks, that's fixed it.
Garry

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] UTF8 encoding problem

On 18/giu/08, at 03:04, Michael Fuhr wrote:

> On Tue, Jun 17, 2008 at 10:48:34PM +0100, Garry Saddington wrote:
>> I am getting illegal UTF8 encoding errors and I have traced it to
>> the £ sign.
>
> What's the exact error message?
>
>> I have set lc_monetary to "lc_monetary = 'en_GB.UTF-8'" in
>> postgresql.conf but
>> this has no effect. How can I sort this problem? Client_encoding
>> =UTF8.
>
> Is the data UTF-8? If the error is 'invalid byte sequence for
> encoding
> "UTF8": 0xa3' then you probably need to set client_encoding to latin1,
> latin9, or win1252.

Why?

--
Giorgio Valoti
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[SQL] order by when using cursors

Hi!

I did some experiments with cursors and found that my data doesn't get
sorted by the "order by"-statement.

Here is what I did:

----------------

CREATE TABLE ta (
a integer NOT NULL,
b integer NOT NULL
);

insert into ta values(3,1);
insert into ta values(1,2);
insert into ta values(4,3);
insert into ta values(2,4);

CREATE OR REPLACE FUNCTION testcur( OUT a integer, OUT b integer )
RETURNS SETOF RECORD AS $$
DECLARE
cur refcursor;
BEGIN
OPEN cur FOR SELECT * FROM ta ORDER BY a DESC;
LOOP
FETCH cur INTO a,b;
IF not found THEN
exit;
ELSE
RETURN NEXT;
END IF;
END LOOP;
CLOSE cur;
END;
$$ LANGUAGE 'PLPGSQL' ;

SELECT * FROM testcur();

----------------

As the result I get:

3 1
1 2
4 3
2 4

Which is not ordered by column a!?

Is this intended?
Am I doing something wrong?

I'm using Postgresql 8.3.1

Patrick

--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql

Re: [SQL] using calculated column in where-clause

Andreas Kretschmer wrote:

>> Do I have to repeat the calculation (which might be even more complex
> yes.

Short and pregnant! :-)

Thanks!
Patrick

--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql

Re: [HACKERS] regex cache

Josh Berkus <josh@agliodbs.com> writes:
> I'm doing some analysis of PostgreSQL site traffic, and am being frequently
> hung up by the compile-time-fixed size of our regex cache (32 regexes, per
> MAX_CACHED_RES). Is there a reason why it would be hard to use work_mem
> or some other dynamically changeable limit for regex caching?

Hmmm ... Spencer's regex library makes a point of hiding its internal
representation of a compiled regex from the calling code. So measuring
the size of the regex cache in bytes would involve doing a lot of
violence to that API. We could certainly allow the size of the cache
measured in number-of-regexes to be controlled, though.

Having said that, I'm not sure it'd help your problem. If your query is
using more than 32 regexes concurrently, it likely is using $BIGNUM
regexes concurrently. How do we fix that?

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [ADMIN] Installation problems RH5 PostgreSQL 8.3.1

"Cliff Pratt" <enkiduonthenet@gmail.com> writes:
> I'm trying to install PostgreSQL and the PostgreSQL libs on RHEL5
> using rpms. I'm getting dependency problems:

> # rpm --test -ivh postgresql-8.3.1-1PGDG.rhel4.x86_64.rpm postgresql-libs-8.3.1-1PGDG.rhel4.x86_64.rpm

[ squint... ] It looks to me like you're trying to install RPMs built
for RHEL4 on RHEL5. Get the correct RPMs.

regards, tom lane

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Re: [lapug] June's Presentation Requirements

On Tue, Jun 17, 2008 at 10:05 PM, Juan Jose Natera <naterajj@gmail.com> wrote:

> My laptop has a VGA port, so a projector that can connect to that
> would be great,

I can't verify if a projector can be made available. Would anyone be
able to bring a projector?

--
Regards,
Richard Broersma Jr.

Visit the Los Angles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

--
Sent via lapug mailing list (lapug@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/lapug

[ADMIN] Installation problems RH5 PostgreSQL 8.3.1

I'm trying to install PostgreSQL and the PostgreSQL libs on RHEL5
using rpms. I'm getting dependency problems:

>>>>># rpm --test -ivh postgresql-8.3.1-1PGDG.rhel4.x86_64.rpm postgresql-libs-8.3.1-1PGDG.rhel4.x86_64.rpm
warning: postgresql-8.3.1-1PGDG.rhel4.x86_64.rpm: Header V3 DSA
signature: NOKEY, key ID 442df0f8
error: Failed dependencies:
libcrypto.so.4()(64bit) is needed by postgresql-8.3.1-1PGDG.rhel4.x86_64
libreadline.so.4()(64bit) is needed by
postgresql-8.3.1-1PGDG.rhel4.x86_64
libssl.so.4()(64bit) is needed by postgresql-8.3.1-1PGDG.rhel4.x86_64
libcrypto.so.4()(64bit) is needed by
postgresql-libs-8.3.1-1PGDG.rhel4.x86_64
libssl.so.4()(64bit) is needed by
postgresql-libs-8.3.1-1PGDG.rhel4.x86_64

I don't understand the dependency on the so.4 libraries, since on
another server the 8.3.1 packages apparently use the so.6 libraries:

>>># ldd /usr/bin/postmaster
libxslt.so.1 => /usr/lib64/libxslt.so.1 (0x0000003ceb400000)
libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x0000003cf0c00000)
libpam.so.0 => /lib64/libpam.so.0 (0x0000003cef800000)
libssl.so.6 => /lib64/libssl.so.6 (0x0000003cf0000000)
libcrypto.so.6 => /lib64/libcrypto.so.6 (0x0000003cedc00000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2
(0x0000003ceec00000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003cec400000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003cea000000)
libm.so.6 => /lib64/libm.so.6 (0x0000003cea800000)
libc.so.6 => /lib64/libc.so.6 (0x0000003ce9c00000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x0000003cef000000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003ced000000)
libz.so.1 => /usr/lib64/libz.so.1 (0x0000003ceb800000)
libaudit.so.0 => /lib64/libaudit.so.0 (0x0000003ced400000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x0000003cee400000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0
(0x0000003cee800000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003cef400000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003cecc00000)
/lib64/ld-linux-x86-64.so.2 (0x0000003ce9800000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003ceac00000)
libsepol.so.1 => /lib64/libsepol.so.1 (0x0000003ceb000000)

The so.4 libraries don't exist on either system!

Any help would be appreciated.

Cheers,

Cliff

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Re: [GENERAL] Need Help Recovering from Botched Upgrade Attempt

Klint Gore wrote:
> Rich Shepard wrote:
>> Despite trying to be careful, I managed to mess up the upgrade from
>> -8.1.4
>> to -8.3.3 on my Slackware-11.0 server/workstation. I expect that someone
>> here will see my error and point me in the right direction to recover a
>> working dbms.
>>
>> Here's what I did:
>>
>> 1.) As a user, I ran pg_dumpall on version 8.1.4 and had that
>> written to
>> /usr4/postgres-backups/.
>>
>> 2.) Created /usr4/pgsql_old/, and copied all of /var/lib/pgsql/
>> there ('cp
>> -a /var/lib/pgsql/* .')

I hope you mean cp -aR , because you need those subdirectories if you're
ever going to try to use the _old copy. Even if you actually did a
recursive copy, if you really copied the data directories with the DB
server running and without executing:

select pg_start_backup('migrate');

or similar before starting the copy then you're going to have problems
using that data. You can copy a working postgresql instance's data
directories, but only if you've enabled WAL logging and you tell Pg
about it so it can write appropriate markers for recovery.

It would probably have been better to:

- pg_dumpall

- STOP THE 8.1 DATABASE SERVER and make sure it's stopped (no postmaster
or postgres processes hanging around).

- Make the old DB server binaries non-executable with chmod and/or
remove them from the PATH

- mv /var/lib/pgsql to /usr4/pgsql_old

- /path/to/8.3/bin/initdb -D /var/lib/pgsql/data

- Adjust postgresql.conf and pg_hba.conf as required

- Start the 8.3 server

- pg_restore all databases from dumps

Right now, you probably need to make REALLY sure you've put a copy of
those dumps somewhere safe, because I suspect your _old copy will be
useless. Then use 8.3's initdb on a new, empty directory, verify that
the config files are correct, and start the 8.3 server.

--
Craig Ringer

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[lapug] June's Presentation Requirements

Jaun,

For your presentation, will you need any equipment? (projectors, ???)

--
Regards,
Richard Broersma Jr.

Visit the Los Angles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug

--
Sent via lapug mailing list (lapug@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/lapug

[pgsql-jobs] Posting Request for a Postgres Guru

Good evening:

 

I would appreciate your assistance in posting the follow job announcement to the PostgreSQL job list:

 

Postgres Guru Needed to Propel Fast-Growing Company to the Next Level!

Job Id:  WTHT-PSDBA

WhiteHat Security offers you an amazing opportunity to leverage your PostgreSQL expertise as our Database Administrator. A pivotal member of our team, you will work with a rapidly expanding multi-terabyte Postgres database, and guide us as we move from a centralized to decentralized environment. In this fast-paced, high-transaction setting, you will be constantly challenged as you tune and optimize our databases, ensuring that they operate at peak performance, and you will solve our most important storage issues including how best to distribute co-location facilities to guarantee optimal disaster recovery. The career-defining opportunity to work with a company truly at the bleeding edge of Postgres database management has presented itself. Go for it.

WhiteHat Security was founded to provide a comprehensive solution to the growing problem of website security and has quickly become a leading provider of website security services. WhiteHat develops comprehensive, easy-to-use, cost-effective solutions that enable companies to secure valuable customer data, meet federal compliance standards, and maintain customer confidence. Our team has worked at companies such as Symantec, Verisign, Tripwire, and Yahoo!, and WhiteHat executives are frequent speakers at security industry events such as ISSA, BlackHat, ISACA and more. We are growing at an impressive pace, and we are the right place for bright, creative, energetic people looking to get in on the ground floor of a fantastic opportunity. Find out more about WhiteHat and why we're so good at what we do: www.whitehatsec.com

As our Postgres Database Administrator based in our Santa Clara, California headquarters, your primary mission will be to manage and ensure the availability and performance of our database infrastructure. In this role, you will partner with our developers to come up with solutions to problems that often challenge the open-source environment, using your keen troubleshooting ability and knowledge of cutting-edge technology. Your solid command of PostgreSQL software will be put to the test as you analyze its interactions with both OS and hardware (you will work with Postgres 100% of the time). Your ability to extract and comprehend both I/O statistics (along with the underlying hardware characteristics) will be critical, as you will be counted on to recommend hardware upgrades and purchases. In addition, your comprehension of PostgreSQL’s own I/O stats will allow you to quickly zoom in on any query bottlenecks and architectural flaws. You can count on utilizing your rock-solid scripting experience using Perl, SQL (Python and C a big plus) to create complex scripts and tools for use in bridging any gaps in our database. Your comfort using PgFouine for performance profiling and query playback for QA environments, coupled with your ability to read query planner analysis and adjust query planner parameters to optimize/help planner decisions will really set you apart from the crowd. Finally, your understanding of general scalability issues of horizontal and vertical partitioning, as well as the issues involved with using database proxying, will allow you to dive right in and quickly get to work. With all that will be thrown your way, your sense of humor can't fail you, and we will make sure you get the support you need to assure your continued success in a role that is, admittedly, not for the faint of heart. But you're up for this challenge -- aren't you?

To apply for this position or refer someone you know, please use our online interview system managed by Accolo:

http://jobs.accolo.com/14199

Once you have completed the interview, your information will be forwarded to the hiring authority for decisions on next steps.

Related Keywords:

PostgreSQL, log shipping, PITR, SLONY, debian package releases, Debian GNU/Linux, Perl, SQL, python, C, uniform access rights, PgFouine, query playback, PgBouncer, PgPool, WalMgr, pg_standby, database proxying, PlProxy, DBA, Database Administrator, MySQL, open source database, scripting, monitoring, logging, replication, SQL queries, relational database, normalization, Linux, Unix, coding, Senior MySQL DBA

 

****

 

Many thanks in advance for your kind consideration.

 

Best regards, Greg

 

 

 

Greg Vargas, PHR

Hiring Consultant

Accolo, Inc.
415.755.1252
gvargas@accolo.com
www.accolo.com

Join our team!

 

 

Re: [GENERAL] Clustering with minimal locking

On Jun 17, 2008, at 11:37 AM, Scott Ribe wrote:
>> BOOM! Deadlock.
>
> No more likely than with the current cluster command. Acquiring the
> lock is
> the same risk; but it is held for much less time.

Actually, no (at least in 8.2). CLUSTER grabs an exclusive lock
before it does any work meaning that it can't deadlock by itself. Of
course you could always do something like

BEGIN;
SELECT * FROM a;
CLUSTER .. ON a;
COMMIT;

Which does introduce the risk of a deadlock, but that's your fault,
not Postgres.
--
Decibel!, aka Jim C. Nasby, Database Architect decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828

Re: [GENERAL] postgres-devel for 8.3.3

Graeme Gemmill <graeme@gemmill.name> writes:
> I've downloaded v8.3.3 and successfully installed it. I now have to
> configure/make/install an application that will use PostgreSQL, and
> think I need the postgresql-devel that corresponds to 8.3.3. Can someone
> point me to where it is please?

Er ... wherever you got the base 8.3.3 RPM from. You really can't
mix-and-match on this, because different builders might have picked
different configuration options. You need to get the exact matching
-devel RPM.

regards, tom lane

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Need Help Recovering from Botched Upgrade Attempt

On Tuesday 17 June 2008 7:18 pm, Rich Shepard wrote:
> On Wed, 18 Jun 2008, Klint Gore wrote:
> >> 5.) Built postgresql-8.3.3 using the SlackBuild script, then ran
> >> 'upgradepkg postgresql-8.3.3*tgz'; other than reporting not finding an
> >> expected pid file, that went smoothly.
> >
> > Is there an initdb in here somewhere? Or is the 8.3 server trying to
> > start with an 8.1 file structure?
>
> Klint,
>
> Backed up a couple of steps, and tried again. Removed postgresql-8.3.3;
> deleted all contents of /var/lib/pgsql/data (because initdb is supposed to
> create the contents, if I correctly read the Postgresql book); re-installed
> postgresql-8.3.3; ran (as user postgres) 'initdb -D /var/lib/pgsql/data'.
> Nothing!

Define nothing. When you ran initdb there where no messages? Also when in
doubt I use the full path /var/lib/pgsql/bin/initdb as you have an old
version of initdb present in the old version directory you copied. When you
have two versions present at the same time it is easy to get cross reference
problems.

>
> I've really FUBARed this and don't understand how, or what to do to
> recover.
>
> Thanks,
>
> Rich
>
> --
> Richard B. Shepard, Ph.D. | Integrity Credibility
> Applied Ecosystem Services, Inc. | Innovation
> <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863

--
Adrian Klaver
aklaver@comcast.net

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Need Help Recovering from Botched Upgrade Attempt

Rich Shepard wrote:
> On Wed, 18 Jun 2008, Klint Gore wrote:
>
> >> 5.) Built postgresql-8.3.3 using the SlackBuild script, then ran
> >> 'upgradepkg postgresql-8.3.3*tgz'; other than reporting not finding an
> >> expected pid file, that went smoothly.
> >>
> > Is there an initdb in here somewhere? Or is the 8.3 server trying to start
> > with an 8.1 file structure?
>
> Klint,
>
> Backed up a couple of steps, and tried again. Removed postgresql-8.3.3;
> deleted all contents of /var/lib/pgsql/data (because initdb is supposed to
> create the contents, if I correctly read the Postgresql book); re-installed
> postgresql-8.3.3; ran (as user postgres) 'initdb -D /var/lib/pgsql/data'.
> Nothing!
>
> I've really FUBARed this and don't understand how, or what to do to
> recover.
>
> Thanks,
>
>
Make sure that initdb is the version you want
initdb --version

then
initdb -E UTF8 -D /var/lib/pgsql/data

then post the output of that.

kllint.

--
Klint Gore
Database Manager
Sheep CRC
A.G.B.U.
University of New England
Armidale NSW 2350

Ph: 02 6773 3789
Fax: 02 6773 3266
EMail: kgore4@une.edu.au

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Need Help Recovering from Botched Upgrade Attempt

On Wed, 18 Jun 2008, Klint Gore wrote:

>> 5.) Built postgresql-8.3.3 using the SlackBuild script, then ran
>> 'upgradepkg postgresql-8.3.3*tgz'; other than reporting not finding an
>> expected pid file, that went smoothly.
>>
> Is there an initdb in here somewhere? Or is the 8.3 server trying to start
> with an 8.1 file structure?

Klint,

Backed up a couple of steps, and tried again. Removed postgresql-8.3.3;
deleted all contents of /var/lib/pgsql/data (because initdb is supposed to
create the contents, if I correctly read the Postgresql book); re-installed
postgresql-8.3.3; ran (as user postgres) 'initdb -D /var/lib/pgsql/data'.
Nothing!

I've really FUBARed this and don't understand how, or what to do to
recover.

Thanks,

Rich

--
Richard B. Shepard, Ph.D. | Integrity Credibility
Applied Ecosystem Services, Inc. | Innovation
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [HACKERS] Crash in pgCrypto?

Coming to this thread a bit late as I've been out of email
connectivity for the past week...

On Tue, Jun 17, 2008 at 2:43 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> In any case, trying to define a module as a schema doesn't help at all
> to solve the hard problem, which is how to get this stuff to play nice
> with pg_dump. I think that the agreed-on solution was that pg_dump
> should emit some kind of "LOAD MODULE foo" command, and *not* dump any
> of the individual objects in the module. We can't have that if we try
> to equate modules with schemas instead of making them a new kind of
> object.

This is certainly the end result that I'd like, and intend to work
towards. My main concern has been cases where a module-owned table
gets updated with data that would not be recreated/updated by the LOAD
MODULE in the dump. PostGIS support tables are one example of this,
PL/Java classpath / function information is another. There are
probably many more.

I see two potential solutions:

a) explicitly mark such tables as requiring data to be dumped somehow,
and have pg_dump emit "upsert" statements for all rows in the table.

b) allow modules to define a function that can pg_dump can call to
emit appropriate extra restore commands, above whatever LOAD MODULE
foo does. This has the downside of requiring more work from module
owners (though perhaps a default function that effectively does option
a) could be provided), with a potential upside of allowing module
dumps to become upgrade-friendly by not being tied to a particular
version's table layout.

Thoughts?

Tom

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] pg_dump fails to include sequences, leads to restore fail in any version

On Tue, Jun 17, 2008 at 6:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Alvaro Herrera <alvherre@commandprompt.com> writes:
> Jeffrey Baker escribió:
>> The table was originally created this way:

> Okay, but was it created on 8.1 or was it already created on an older
> version and restored?  I don't see this behavior if I create it in 8.1
> -- the field is dumped as SERIAL, unlike what you show.

There's something interesting in the original report:

> --
> -- Name: transaction_transaction_id_seq; Type: SEQUENCE SET; Schema: mercado; Owner: prod
> --
>
> SELECT
> pg_catalog.setval(pg_catalog.pg_get_serial_sequence('transaction_backup',
                                                      ^^^^^^^^^^^^^^^^^^
> 'transaction_id'), 6736138, true);

So pg_dump found a pg_depend entry linking that sequence to some table
named transaction_backup, not transaction.  That explains why
transaction isn't being dumped using a SERIAL keyword --- it's not
linked to this sequence.  But how things got this way is not apparent
from the stated facts.

Hrmm, I think that's a bit of a red herring.  I probably should not have pasted that part of the dump, because it's misleading.  There really is a table transaction_backup, definition is the same as transaction.

Reading from that part of the dump again, just for clarity:

--
-- Name: transaction_backup; Type: TABLE; Schema: mercado; Owner: prod; Tablespace:
--

CREATE TABLE transaction_backup (
    transaction_id serial NOT NULL,
    buyer_account_id integer,
    seller_account_id integer,
    date date,
    item_id integer,
    source text
);


ALTER TABLE mercado.transaction_backup OWNER TO prod;

--
-- Name: transaction_transaction_id_seq; Type: SEQUENCE SET; Schema: mercado; Owner: prod
--

SELECT pg_catalog.setval(pg_catalog.pg_get_serial_sequence('transaction_backup', 'transaction_id'), 6736139, true);


--
-- Name: transaction; Type: TABLE; Schema: mercado; Owner: prod; Tablespace:
--

CREATE TABLE "transaction" (
    transaction_id integer DEFAULT nextval('transaction_transaction_id_seq'::regclass) NOT NULL,
    buyer_account_id integer,
    seller_account_id integer,
    date date,
    item_id integer,
    source text
);


ALTER TABLE mercado."transaction" OWNER TO prod;

The two tables are defined the same way, but one of them gets dumped with a SERIAL declaration and the other gets dumped with a DEFAULT nextval().

Is it possible that pg_dump became confused if transaction was renamed transaction_backup and then redefined?  I can't guarantee that did in fact happen, but it's within the realm of possibility.  I don't see the backup table in the sql source code for this product, so it's likely that it was created by a user in the course of maintenance.

 

One possibility is that Jeffrey is getting bit by this bug or
something related:
http://archives.postgresql.org/pgsql-bugs/2006-07/msg00021.php

I don't think it's that one.  All this stuff is in the same schema (and in any case the dump file contains all schemas).

 

There are links to some other known serial-sequence problems in 8.1
in this message:
http://archives.postgresql.org/pgsql-hackers/2006-08/msg01250.php

That one seems closer to the point.

-jwb

[BUGS] BUG #4252: SQL stops my graic cards

The following bug has been logged online:

Bug reference: 4252
Logged by: Andreas Andersson
Email address: andreaswandersson@hotmail.com
PostgreSQL version: SQL 2.8
Operating system: Vista SP1
Description: SQL stops my graic cards
Details:

Post this bug on pockertracker forum:
http://www.pokertracker.com/forums/viewtopic.php?f=29&t=7907

----------------------------------------------
have used PT2, SQL and Vista for and long time and everything has worked
fine with dual screens on GeForce 8800
I woke up this sunday and one screen was black. Then only thing that happend
was that SP1 had been download/installed. I spent 10 hours on uninstalling,
repair windows, and finaly format c: then it all statred to work again, I
installed PT2 , SQL and SP1, sucess until i reboot, and quess what, one
screen goes black again.

On monday I left my computer to a shop, they change the grafic card to MSI
NX 8800 GTS. Installed vista whit SP1 and told me it works perfect with dual
screens. cost me 500$
This morning I picked up my computer and everything was running good untill,
the first thing I did, was installing PT2 and SQL, guess what, one screen
turns black after reboot.

Then I get it, don't know how but SQL 2.8 fuck up my grafic card with vista
SP1. I unistall SQL 2.8 and both screens, reboot and both screens works
again!!
But I still want PT2 and SQL on my poker computer so I try so i try to
install latest SQL 3.3 and everythings seems to be good for I while but then
one screen black again and my computer freaks out.

This is so wierd., and now i´m on format c: for the 5:e time and installing
vista again.

But I will never install SQL again untill I get a good answer here. I have
spent like 2-4 days on this problem now and is so sick., I´m sure that
Vista SP1 whit SQL = problems whith = Gefroce 8800 ot MSI NX 8800 GTS

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[JDBC] insert data into partitioned tables via Java application

I am trying to do an insert data into EDB partitioned tables via front end
application (Java) but the application failing to do an insert. The problem
I identified is since the insert happening into partitioned tables in the
background when you do an insert into base table, so the insert returning
returning Zero rows affected message back to application. So it is failing,
is there any work-around for this.

Any help will be greatly appreciated.

Thanks,
Cap20.
--
View this message in context: http://www.nabble.com/insert-data-into-partitioned-tables-via-Java-application-tp17957653p17957653.html
Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com.

--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc

Re: [GENERAL] Error when trying to drop a tablespace

Albe Laurenz wrote:
> Cyril SCETBON wrote:
>
>>>> I get the following error :
>>>>
>>>> postgres=# DROP TABLESPACE IF EXISTS my_tbs;
>>>> ERROR: tablespace "my_tbs" is not empty
>>>>
>>>> I've searched in pg_class and I'm not able to find a relation which
>>>> refers to my_tbs with :
>>>>
>>>> postgres=# select * from pg_class where reltablespace=100456;
>>>>
>>>>
>>> [...]
>>>
>>>
>>>> (0 rows)
>>>>
>>>> 100456 has been found with :
>>>>
>>>> /oid2name -s|grep my_tbs
>>>>
>>>> Any idea ?
>>>>
>>> You can find the dependent objects with:
>>>
>>> SELECT t.relname AS catalog, d.objid AS oid_dependent
>>> FROM pg_catalog.pg_class t JOIN
>>> pg_catalog.pg_depend d ON (t.oid = d.classid)
>>> WHERE refobjid = 100456;
>>>
>> postgres=# SELECT t.relname AS catalog, d.objid AS oid_dependent
>> postgres-# FROM pg_catalog.pg_class t JOIN
>> postgres-# pg_catalog.pg_depend d ON (t.oid = d.classid)
>> postgres-# WHERE refobjid = 100456;
>> catalog | oid_dependent
>> ---------+---------------
>> (0 rows)
>>
>> nothing...
>>
>
> Hmm.
> Find out the directory:
>
> SELECT oid, spclocation FROM pg_catalog.pg_tablespace WHERE spcname = 'my_tbs';
>
> is there anything in this directory?
>
cd spclocation

find .
.
./100456
./100456/100738
./100456/102333
./100456/103442
./100456/102618
./100456/104159
./100456/101234
./100456/102658
./100456/104477
./100456/101031
./100456/10746
./100456/102680
./100456/103344
./100456/100711
./100456/103519
./100456/102154
./100456/103111
./100456/102613
./100456/104210
./100456/103474
./100456/103784
./100456/103597
./100456/103173
./100456/103160
./100456/100962
./100456/100938
./100456/101375
./100456/103871
./100456/101410
./100456/102151
./100456/104910
./100456/103133
./100456/101778
./100456/102712
./100456/100586
./100456/103466
./100456/101976
./100456/103789
./100456/100911
./100456/103680
./100456/101605
./100456/101858
./100456/101840
./100456/102352
./100456/102047
./100456/104272
./100456/101949
./100456/104907
./100456/102517
./100456/103775
./100456/104527
./100456/102085
./100456/101490
./100456/103333
./100456/102592
./100456/103970
./100456/104549
./100456/101839
./100456/104175
./100456/101024
./100456/104072
./100456/101914
./100456/103677
./100456/100944
./100456/101160
./100456/101135
./100456/102296
./100456/2663
./100456/101818
./100456/104434
./100456/101928
./100456/103469
./100456/100719
./100456/101383
./100456/1259
./100456/102015
./100456/103503
./100456/100650
./100456/103255
./100456/100746
./100456/100616
./100456/2602
./100456/102479
./100456/101776
./100456/102549
./100456/101485
./100456/103559
./100456/102607
./100456/101880
./100456/102090
./100456/101061
./100456/102903
./100456/104365
./100456/103373
./100456/103584
./100456/101565
./100456/101389
./100456/102527
./100456/103888
./100456/101231
./100456/2601
./100456/103802
./100456/102519
./100456/101317
./100456/102504
./100456/104967
./100456/102423
./100456/102224
./100456/102495
./100456/103194
./100456/104931
./100456/103885
./100456/102637
./100456/102480
./100456/103552
./100456/104383
./100456/101720
./100456/103039
./100456/101397
./100456/102176
./100456/102482
./100456/101648
./100456/102552
./100456/103757
./100456/103152
./100456/104893
./100456/104037
./100456/103810
./100456/104501
./100456/104896
./100456/2608
./100456/101309
./100456/102869
./100456/101816
./100456/101127

....
> Yours,
> Laurenz Albe
>

--
Cyril SCETBON - Ingénieur bases de données
AUSY pour France Télécom - OPF/PORTAILS/DOP/HEBEX

Tél : +33 (0)4 97 12 87 60
Jabber : cscetbon@jabber.org
France Telecom - Orange
790 Avenue du Docteur Maurice Donat
Bâtiment Marco Polo C2 - Bureau 202
06250 Mougins
France

***********************************
Ce message et toutes les pieces jointes (ci-apres le 'message') sont
confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration. Le Groupe France
Telecom decline toute responsabilite au titre de ce message s'il a ete
altere, deforme ou falsifie.
Si vous n'etes pas destinataire de ce message, merci de le detruire
immediatement et d'avertir l'expediteur.
***********************************
This message and any attachments (the 'message') are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. France Telecom Group shall not be
liable for the message if altered, changed or falsified.
If you are not recipient of this message, please cancel it immediately and
inform the sender.
************************************

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [pgsql-de-allgemein] Spalte mit not null und deferrable hinzufügen

am Tue, dem 17.06.2008, um 11:36:26 +0200 mailte Thomas Guettler folgendes:
> Hallo,
>
> ich möchte eine Spalte mit einem initially deferred not null constraint
> hinzufügen.
>
> db=# alter table mytable add column "time" timestamp with time zone not
> null deferrable initially deferred;
> FEHLER: falsch platzierte DEFERRABLE-Klausel
>
> Laut Doku müsste der Befehl eigentlich funktionieren:

Nein, laut Doku ebend grad nicht:

Currently, only foreign key constraints are affected by this setting.

http://www.postgresql.org/docs/8.3/interactive/sql-set-constraints.html
unter dem Teil, der DEFERRED beschreibt.

Andreas
--
Andreas Kretschmer
Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header)
GnuPG-ID: 0x3FFF606C, privat 0x7F4584DA

http://wwwkeys.de.pgp.net

--
Sent via pgsql-de-allgemein mailing list (pgsql-de-allgemein@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-de-allgemein

[COMMITTERS] stackbuilder - wizard: Add MacOSX bundle info, and ensure the wxWidgets

Log Message:
-----------
Add MacOSX bundle info, and ensure the wxWidgets version is 2.8.x

Modified Files:
--------------
wizard:
CMakeLists.txt (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/CMakeLists.txt.diff?r1=1.1&r2=1.2)

--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

Re: [PERFORM] Tsearch2 Initial Search Speed

Alan Hodgson wrote:
> It's because everything is cached, in particular the relevant rows from
> the "email" table (accessing which took 22 of the original 27 seconds).
>
> The plan looks good for what it's doing.
>
> I don't see that query getting much faster unless you could add a lot more
> cache RAM; 30K random IOs off disk is going to take a fair bit of time
> regardless of what you do.
>
>

Thanks Alan, I guessed that the caching was the difference, but I do not
understand why there is a heap scan on the email table? The query seems
to use the email_fts_index correctly, which only takes 6 seconds, why
does it then need to scan the email table?

Sorry If I sound a bit stupid - I am not very experienced with the
analyse statement.

--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

[COMMITTERS] stackbuilder - wizard: Add a CMake build file

Log Message:
-----------
Add a CMake build file

Added Files:
-----------
wizard:
CMakeLists.txt (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/CMakeLists.txt?rev=1.1&content-type=text/x-cvsweb-markup)

--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

Re: [BUGS] UUIDs generated using ossp-uuid on windows not unique

On Tue, Jun 17, 2008 at 10:25 AM, Hiroshi Saito
<z-saito@guitar.ocn.ne.jp> wrote:
> Hi.
>
> Um, I will arrange information and write wiki. . Is it a suitable place?

A README file at http://winpg.jp/~saito/pg_work/OSSP_win32/ would be enough.

> This is some information. http://winpg.jp/~saito/pg_work/OSSP_win32/
> uuid-ossp.dll(MinGW compile) is this.
> http://winpg.jp/~saito/pg_work/OSSP_win32/pg8.3.3-win-bin-uuid-ossp.zip

We need a VC++ .lib for the installer. When I tried last time, I
unpacked the source, replaced the headers with those in the msvc
directory, and applied your patch. The build then failed with various
missing (unix-specific) headers iirc. Do you have a set of dummy
replacements someplace in your build environment?

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[pgsql-de-allgemein] Spalte mit not null und deferrable hinzufügen

Hallo,

ich möchte eine Spalte mit einem initially deferred not null constraint
hinzufügen.

db=# alter table mytable add column "time" timestamp with time zone not
null deferrable initially deferred;
FEHLER: falsch platzierte DEFERRABLE-Klausel

Laut Doku müsste der Befehl eigentlich funktionieren:

alter table Doku

ADD [ COLUMN ] /column/ /type/ [ /column_constraint/ [ ... ] ]

create table Doku:

where /column_constraint/ is:

[ CONSTRAINT /constraint_name/ ]
{ NOT NULL |
NULL |
UNIQUE /index_parameters/ |
PRIMARY KEY /index_parameters/ |
CHECK ( /expression/ ) |
REFERENCES /reftable/ [ ( /refcolumn/ ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
[ ON DELETE /action/ ] [ ON UPDATE /action/ ] }
[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]

select version();

version
--------------------------------------------------------------------------------------------
PostgreSQL 8.2.6 on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC)
4.2.1 (SUSE Linux)

Hat jemand Hinweise?

Thomas

--
Thomas Guettler, http://www.thomas-guettler.de/
E-Mail: guettli (*) thomas-guettler + de

--
Sent via pgsql-de-allgemein mailing list (pgsql-de-allgemein@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-de-allgemein

Re: [GENERAL] PostgreSQL and AMD?

Dear Greg,

Thanks for your valuable and extensive reply. You were right that it is
the HP machine the client is wanting, I did also find a configuration
that has a Quad Core Intel processor and they will probably go with that
for continuity with their current hardware. The PostgreSQL database on
the server is to be used as an authentication gateway for enterprise
installations of SAP, SQL Server and a bunch of GIS and other data
applications, so there won't be a big processing or data transfer load.
There will be two identical machines each with a hot swap drive bay as
well as an internal 160GB drive. Initially there will only be around 50
non concurrent users so again, low load. I have used PostgreSQL for
around four years, but always on Intel chipsets and I had never thought
to investigate processor brands. When the client mentioned AMD I thought
"uh oh" this could be a black hole here.

I note your comments about disk controllers and will investigate that
area too for our next, larger, install.

Thanks again and regards

John

Greg Smith wrote:
> On Sun, 15 Jun 2008, John Tregea wrote:
>
>> The machines would be running Windows XP Pro (our clients
>> requirement). Can anyone tell me if PostgreSQL runs fine on the AMD
>> platform and specifically does anyone have experience with the AMD
>> Phenom™ Quad Core Processors 9600B.
>
> Once you've settled on Windows as your PostgreSQL platform, you've
> kind of given up on prioritizing performance at that point--there's a
> couple of issues that limit how good that can possibly be no matter
> what hardware you throw at it. Details like which processor you're
> using are pretty trivial in comparision. Also, the real questions you
> should be asking are ones like "did I get a good disk controller for
> database use?" which is a really serious concern in this space. My
> guess is you're talking about an HP DC5850. I am rather skeptical of
> the disk subsystem in that system (at most two disks and just a crappy
> BIOS RAID) working well in a database context. It's probably fine for
> a non-critical system, but I wouldn't run a business on it.
>
> In general, AMD has been lagging just a bit behind Intel's products
> recently on systems with a small number of sockets. There are
> occasional reports where multi-socket multi-core systems from AMD are
> claimed to do better than similar Intel systems due to AMD's better
> bus design, I haven't seen that big difference either way myself in
> recent products.
>
> I've been using several different types of Opteron and X2 processors
> systems from AMD the last couple of years and typically they work just
> fine. But Phenom has really been a troubled platform launch for AMD
> and I think that's why nobody has offered any suggestions to you
> yet--I haven't heard any reports from people using that chip in a
> server environment yet.
>
> --
> * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [BUGS] UUIDs generated using ossp-uuid on windows not unique

Hi.

Um, I will arrange information and write wiki. .
Is it a suitable place?

This is some information.

http://winpg.jp/~saito/pg_work/OSSP_win32/
uuid-ossp.dll(MinGW compile) is this.
http://winpg.jp/~saito/pg_work/OSSP_win32/pg8.3.3-win-bin-uuid-ossp.zip

Regards,
Hiroshi Saito

----- Original Message -----
From: "Dave Page" <dpage@postgresql.org>

> On Tue, Jun 17, 2008 at 5:21 AM, Hiroshi Saito <z-saito@guitar.ocn.ne.jp> wrote:
>> Hi.
>>
>> Sorry, late the information.....
>> My patch was applied after the review of Ralf-san. However, The timing of a
>> release was different. Then, patch is only current CVS-HEAD.
>> http://cvs.ossp.org/chngview?cn=6001
>>
>> I thought that this problem was very important. It was sufficient reason to
>> apply to 8.3.3 of pginstaller. Therefore, It should return the result of a
>> wish.
>
> It's not in 8.3.3 - I'm still waiting for details of how to build it,
> as it's not exactly obvious.
>
> --
> Dave Page
> EnterpriseDB UK: http://www.enterprisedb.com
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [pgadmin-support] help

On Tue, Jun 17, 2008 at 9:13 AM, daniel <daniel@ascent-soft.ro> wrote:
> Hello ! I'm using your application Pgadmin a lot.
> I have a question : where is the server list saved ? i can't find any file
> on my computer with this info.
> I need to install the same configuration on a lot of computers and I can't
> find a quick solution.
>
>
> My OS : Windows Xp

They are stored in the registry on Windows, under
HKEY_CURRENT_USER\Software\pgAdmin III\Servers

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support

Re: [GENERAL] inserting to a multi-table view

Michael Shulman wrote:
> On Mon, Jun 16, 2008 at 10:03 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
>
>>> I can write a trigger
>>> function that does the right thing, with 'INSERT ... RETURNING
>>> person_id INTO ...', but Postgres will not let me add an INSERT
>>> trigger to a view; it says 'ERROR: "studentinfo" is not a table'.
>>>
>> Got a short example of what you've tried so far?
>>
>
> create function ins_st() returns trigger as $$
> declare
> id integer;
> begin
> insert into person (...) values (NEW....) returning person_id into id;
> insert into student (person_id, ...) values (id, NEW....);
> end;
> $$ language plpgsql;
>
> create trigger ins_student before insert on studentinfo
> for each row execute procedure ins_st();
>
> ERROR: "studentinfo" is not a table
>
> Mike
>
>

The only way I could find to make this work is to use a rule and wrap
the inner "insert returning" in a function.

create or replace function newperson (studentinfo) returns setof person as
$$
declare
arec person%rowtype;
begin
for arec in
insert into person (foo,bar) values ($1.foo,$1.bar) returning *
loop
-- insert into address (...) values (arec.person_id, $1....)
-- insert into phone (...) values (arec.person_id, $1....)
return next arec;
end loop;
return;
end;
$$
language plpgsql volatile;
create rule atest as on insert to studentinfo do instead (
insert into student (person_id) select (select person_id from
newperson(new));
);

klint.

--
Klint Gore
Database Manager
Sheep CRC
A.G.B.U.
University of New England
Armidale NSW 2350

Ph: 02 6773 3789
Fax: 02 6773 3266
EMail: kgore4@une.edu.au

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [pgsql-es-ayuda] Crear función con un FOR

Muchas gracias a todos por contestar.
La idea no es marcar uno al azar si no que el select que me filtra en la
tabla de los pedidos ya deja en los que me interesa marcarlo, los mas
urgentes, asi que creo que con las ideas que me habéis dado ya puedo
ordenarlas y sacar lo que necesito, muchas gracias.
En cuanto lo tenga funcionando pongo la solución por si le sirve a
alguien y para ver que os parece.

Gracias.

Miguel Rodríguez Penabad escribió::
> El día 16 de junio de 2008 18:48, el-PRiNCiPiTo
> <el-PRiNCiPiTo@terra.es> escribió:
>
>> Muchas gracias por contestar.
>>
>> Lo que me has dicho no es exactamente lo que estoy intentando hacer. Creo
>> que no lo he explicado muy bien porque no he dicho cual es el motivo de que
>> yo quiera "recorrer las filas".
>> Yo estoy más acostumbrado a programar en otros entornos y entonces mi idea
>> es la siguiente:
>> Con un select limito las filas en las que se va a actuar a las que a mi me
>> interesa (esto de la tabla dos, la que recibe los cambios)
>> Con el for iría pasando por esas filas en las que si quiero actuar y
>> cuando una cumpla la condición que le ponga, la actualiza y luego sale del
>> for, osea que deja de mirar el resto de filas ya que solo quiero cambar una
>> y no todas aunq también cumplan las condiciones.
>>
>
> Creo que este es el problema: Venir de un "entorno de programación" y
> tratar de hacer las cosas en bases de datos de la misma forma.
>
>
>> Para ser mas claro voy a explicar lo que tiene que hacer realmente. Yo
>> tengo una tabla con todos los pedidos y otra en la que inserto la
>> producción. Entonces lo que quiero es que cuando inserte o actualice algo en
>> la tabla producción mire en la tabla pedidos si hay algún pedido de ese
>> producto y de ser así que lo marque como fabricado. Entonces se puede dar el
>> caso de que tenga varios pedidos del mismo producto y que fabrique una
>> unidad, yo no quiero marcar todos lospedidos como fabricados si no el
>> primero que encuentre.
>>
>>
>
> El problema que yo veo es: ¿cual de los pedidos marcas como fabricado?
> ¿uno al azar? yo al menos no le veo sentido, es mas, lo veo erróneo.
> Si los pedidos estuviesen ordenados por algún criterio, podrías usar la opción
> que yo te decía, usar un update pero algo parecido a
>
> update tabla2
> set idmodifica = 1 --no se como quieres modificar
> where idCompara1=NEW.idCompara1
> and idCompara2= NEW.idCompara2 --no se si la condición es así
> and campoordenacion = (select min(campoordenacion) from tabla2
> where idCompara1=NEW.idCompara1
> and idCompara2= NEW.idCompara2)
> Quizás haya otra alternativa más simple, no sé, pero así sólo actualizaríamos
> el primer pedido que cumpla la condición.
>
> Si, de todas formas, quieres seguir "recorriendo filas", podrías
> declarar un cursor
> y hacer un "update... where current of..", que se está comentando en
> otro hilo de la lista.
> Después de hacer ese update haces un "return new;" y ya saldría de la
> función sin
> modificar nada más. Pero en mi opinión ES UNA MALA OPCIÓN. Quizás
> deberías revisar
> el diseño de la bd.
>
> Saludos
>

--
TIP 4: No hagas 'kill -9' a postmaster

Re: [pgsql-it-generale] to_tsvector: errori nella configurazione italiana

Capito il problema.
Praticamente il file italian.stop e' encodato non UTF8 (probabilmente
qualche variabile d'ambiente di mac osx ha fatto casino).

Provo ad allegarti il mio file italian.stop utf8 che funziona correttamente.
Nel caso la mailing list lo rigettasse te lo mando in mail privata.

Ciao
Fede

On Tue, Jun 17, 2008 at 8:28 AM, Giorgio Valoti <giorgio_v@mac.com> wrote:
> On 16/giu/08, at 08:13, Giorgio Valoti wrote:
>
>> […]
>
> Prima di arrendermi volevo chiedere se qualcuno aveva altri suggerimenti. Ho
> aggiornato alla 8.3.3 senza nessun risultato e ho provato lo stesso database
> sotto una SuSE 9.2 dove ho verificato che to_tsvector funziona senza
> problemi. Sono compilati praticamente allo stesso modo: dove può stare la
> differenza?
>
> Ciao
> --
> Giorgio Valoti
> --
> Sent via pgsql-it-generale mailing list (pgsql-it-generale@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-it-generale
>

--
(all opinions expressed are my own)
Federico Campoli
PostgreSQL Consulting -> PGHost http://www.pghost.eu

[pgadmin-support] help

Hello ! I'm using your application Pgadmin a lot.
I have a question : where is the server list saved ? i can't find any file
on my computer with this info.
I need to install the same configuration on a lot of computers and I can't
find a quick solution.

My OS : Windows Xp

--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support

Re: [pgadmin-hackers] Enabling SQL text field in the SQL tab of object dialog

On Tue, Jun 17, 2008 at 8:59 AM, Guillaume Lelarge
<guillaume@lelarge.info> wrote:

>> That can be
>> potentially dangerous if the user has another property dialogue for a
>> sibling object open though (actually that's an issue now iirc - this
>> would just make it far more likely to occur).
>>
>
> What kind of issue are you talking about? can you give me an example?

When you open a properties dialogue, it gets passed a pointer to the
pgObject which it may use right up until it is closed. If you refresh
part of the tree, you delete and recreate all the pgObjects under the
node you refresh, so the dialogue can end up with a pointer to an
object that's been deleted.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

Re: [pgadmin-hackers] Enabling SQL text field in the SQL tab of object dialog

Dave Page a écrit :
> On Mon, Jun 16, 2008 at 11:07 PM, Guillaume Lelarge
> <guillaume@lelarge.info> wrote:
>> OK, this works on my local branch but I still have one issue with it: if the
>> user change the name of a newly created object in the SQL text field, the
>> treeview will display the name available in the name field, not the real one
>> available in the SQL text field.
>
> The only way I can think to handle that is to refresh the parent
> collection, not just the object being modified.

That's also the way I wanted to handle this. But we get back to the
refresh issue. I will need to fix this one.

> That can be
> potentially dangerous if the user has another property dialogue for a
> sibling object open though (actually that's an issue now iirc - this
> would just make it far more likely to occur).
>

What kind of issue are you talking about? can you give me an example?

--
Guillaume.

http://www.postgresqlfr.org

http://dalibo.com

--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

Re: [pgsql-www] Software catalog section improvements

On Mon, Jun 16, 2008 at 7:01 PM, Greg Sabino Mullane <greg@turnstep.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
> On the new Software Catalog er..."Catalogue" page, how does
> one edit an existing entry? There is no contact email to
> do so. While I know I can just bug Dave on this list, the
> public should be told an email address.

Most people will simply email webmaster@ no? We don't list a contact
address on any other forms on the site that I can see.

> I messed up entering "Spree", it should be under Applications
> and has an open source, not a commercial license.

Fixed.

> Also, it might be nice if the "Procedural Languages" section
> mentioned that the builtin languages that are already available,
> lest people stumble across this page and not be aware that
> C, plpgsql, perl, python, and tcl are all available in core.

There's no code for including additional text on each category at
present. We can either add that (noting that the admin interface for
categories is a highly advanced SQL based one) - patches welcome - or
add those languages to the list with a note saying they're in the core
product. Or consider it a non-issue.

Thoughts?

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

--
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www

Re: [pgsql-es-ayuda] Copia y restauracion de base de datos de GForge

En el archivo de respaldo de SQL:

--
-- PostgreSQL database dump
--

-- Started on 2008-06-13 09:47:49 CEST

SET client_encoding = 'UTF8';
SET check_function_bodies = false;
SET client_min_messages = warning;

SET search_path = public, pg_catalog;

ALTER TABLE ONLY public.wiki_version DROP CONSTRAINT wikipageid_fk;
ALTER TABLE ONLY public.user_project_role DROP CONSTRAINT userprojectid_fk;
ALTER TABLE ONLY public.tracker_my_queue DROP CONSTRAINT userid_fk;
[...]
DROP TRIGGER users_ts_update ON public."user";
DROP TRIGGER tracker_item_update_trigg ON public.tracker_item;
DROP TRIGGER tracker_item_ts_update ON public.tracker_item;
[...]
DROP RULE wikipagefilesystemdelete_rule ON public.wiki_version;
DROP RULE wikipage_association_delete_rule ON public.wiki_page;
DROP RULE trackeritem_insert_rule ON public.tracker_item;
[...]
DROP INDEX public.wikiversion_wikipageidpageversion;
DROP INDEX public.wikipage_secionrefidpagename;
DROP INDEX public.users_idxfti;
[...]
ALTER TABLE ONLY public.wiki_version DROP CONSTRAINT wiki_version_pkey;
ALTER TABLE ONLY public.wiki_page DROP CONSTRAINT wiki_page_pkey;
ALTER TABLE ONLY public.wiki_page_link DROP CONSTRAINT wiki_page_link_pkey;
[...]
DROP TABLE public.wiki_version;
DROP TABLE public.wiki_page_link;
DROP TABLE public.wiki_page;
[...]
DROP SEQUENCE public.user_project_user_project_id_seq;
[...]
DROP OPERATOR public.= (tsvector, tsvector);
DROP OPERATOR public.<> (tsvector, tsvector);
DROP OPERATOR public.<= (tsvector, tsvector);
DROP OPERATOR public.< (tsvector, tsvector);
DROP FUNCTION public.update_vectors();
DROP FUNCTION public.update_last_modified_date();
DROP FUNCTION public.tsvector_ne(tsvector, tsvector);
DROP FUNCTION public.tsvector_lt(tsvector, tsvector);
DROP FUNCTION public.tsvector_le(tsvector, tsvector);
DROP FUNCTION public.tsvector_gt(tsvector, tsvector);
[...]
DROP TYPE public.tokentype;
DROP TYPE public.tokenout;
DROP TYPE public.statinfo;
[...]
DROP PROCEDURAL LANGUAGE plpgsql;
DROP SCHEMA public;
--
-- TOC entry 4 (class 2615 OID 2200)
-- Name: public; Type: SCHEMA; Schema: -; Owner: postgres
--

CREATE SCHEMA public;
[...]
--
-- TOC entry 584 (class 2612 OID 16387)
-- Name: plpgsql; Type: PROCEDURAL LANGUAGE; Schema: -; Owner:
--

CREATE PROCEDURAL LANGUAGE plpgsql;

--
-- TOC entry 79 (class 1255 OID 16557)
-- Dependencies: 4
-- Name: gtsvector_in(cstring); Type: FUNCTION; Schema: public; Owner: postgres
--

CREATE FUNCTION gtsvector_in(cstring) RETURNS gtsvector
AS '$libdir/tsearch2', 'gtsvector_in'
LANGUAGE c STRICT;

ALTER FUNCTION public.gtsvector_in(cstring) OWNER TO postgres;
[...]
CREATE TABLE wiki_version (
wiki_version_id serial NOT NULL,
wiki_page_id integer NOT NULL,
page_version integer NOT NULL,
posted_by integer NOT NULL,
refs text,
last_modified_date timestamp with time zone DEFAULT now(),
score integer,
hits integer,
create_date timestamp with time zone
);

ALTER TABLE public.wiki_version OWNER TO gforge;

--
-- TOC entry 2827 (class 0 OID 0)
-- Dependencies: 1640
-- Name: wiki_version_wiki_version_id_seq; Type: SEQUENCE SET; Schema:
public; Owner: gforge
--

SELECT pg_catalog.setval(pg_catalog.pg_get_serial_sequence('wiki_version',
'wiki_version_id'), 7, true);

--
-- TOC entry 2704 (class 0 OID 16956)
-- Dependencies: 1613
-- Data for Name: activity_log; Type: TABLE DATA; Schema: public; Owner: gforge
--

COPY activity_log (activity_date, project_id, page, activity_type) FROM stdin;
\.

--
-- TOC entry 2749 (class 0 OID 18141)
COPY association (section, ref_id, to_section, to_ref_id, "comment") FROM stdin;
trackeritem 10 trackeritem 12 Es necesario
trackeritem 10 trackeritem 11 Es necesario
trackeritem 18 trackeritem 5 TambiÃ(c)n en el upgrade
trackeritem 74 trackeritem 18 Relacionado
trackeritem 112 trackeritem 95 Asociado a esta tarea
trackeritem 18 trackeritem 134
trackeritem 78 trackeritem 143 Tarea Fran
trackeritem 167 trackeritem 106 Puede necesitar
tambiÃ(c)n la tarjetería Avaya que comenta Dani.
\.

--
-- TOC entry 2667 (class 0 OID 16658)
-- Dependencies: 1554
-- Data for Name: audit_trail; Type: TABLE DATA; Schema: public; Owner: gforge
--

COPY audit_trail (audit_trail_id, change_date, user_id, section,
ref_id, field_name, new_value, old_value) FROM stdin;
1 2008-05-21 09:58:38.326763+02 103 user_project 4
\N 103 \N
[...]

Como ves, primero borra toda la BBDD, ya que el pg_dump le paso la
opcion -c, y después crea la BBDD, y por último hace el copy.

Da errores desde el principio, aunque existen todos los datos, y la
base de datos...

No lo entiendo... :S

El 17/06/08, Clemente López Giner <clemenlg@gmail.com> escribió:
> Restaurando la copia de la BBDD de
> /backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql
> SET
> SET
> SET
> SET
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:13:
> ERROR: no existe la restricción «wikipageid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:14:
> ERROR: no existe la restricción «userprojectid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:15:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:16:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:17:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:18:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:19:
> ERROR: no existe la relación «public.users_idx»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:20:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:21:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:22:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:23:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:24:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:25:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:26:
> ERROR: no existe la restricción «userid_fk»
> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:27:
> ERROR: no existe la restricción «userid_fk»
>
> Eso es lo primero que saca, como ves, no parece que de ninguno acerca de
> copy...
>
> 2008/6/13, Alvaro Herrera <alvherre@alvh.no-ip.org>:
>> Clemente López Giner escribió:
>>> Para crear la copia de la bbdd lo he hecho con pg_dump:
>>> pg_dump -c -v -f $ARCHIVEROOT/$INCREMENTDIR/$BACKUP_BBDD -U $USERNAME
>>> $DBNAME
>>> Y para restaurarla, con:
>>> psql -f $ARCHIVEROOT/$INCREMENTDIR/$BACKUP_BBDD -d $DBNAME -U $USERNAME
>>>
>>> Pero nada, me sigue dando errores
>>>
>>> Algunos errores al restaurarlo (me da muchos):
>>> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:32134:
>>> ERROR: error de sintaxis en o cerca de «1» en el carácter 1
>>
>> [...]
>>
>> Debe haber errores antes que esos. Por favor muestra los primeros
>> errores que da. Tiene que haber uno sobre falla de la orden COPY, antes
>> que este error de sintaxis.
>>
>> PD: por favor no te olvides de copiar la lista.
>>
>> --
>> Alvaro Herrera
>> http://www.PlanetPostgreSQL.org/
>> "En el principio del tiempo era el desencanto. Y era la desolación. Y
>> era
>> grande el escándalo, y el destello de monitores y el crujir de teclas."
>> ("Sean los Pájaros Pulentios", Daniel Correa)
>>
>
--
TIP 9: visita nuestro canal de IRC #postgresql-es en irc.freenode.net

Re: [pgadmin-hackers] Enabling SQL text field in the SQL tab of object dialog

On Mon, Jun 16, 2008 at 11:07 PM, Guillaume Lelarge
<guillaume@lelarge.info> wrote:
>
> OK, this works on my local branch but I still have one issue with it: if the
> user change the name of a newly created object in the SQL text field, the
> treeview will display the name available in the name field, not the real one
> available in the SQL text field.

The only way I can think to handle that is to refresh the parent
collection, not just the object being modified. That can be
potentially dangerous if the user has another property dialogue for a
sibling object open though (actually that's an issue now iirc - this
would just make it far more likely to occur).

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

Re: [BUGS] UUIDs generated using ossp-uuid on windows not unique

On Tue, Jun 17, 2008 at 5:21 AM, Hiroshi Saito <z-saito@guitar.ocn.ne.jp> wrote:
> Hi.
>
> Sorry, late the information.....
> My patch was applied after the review of Ralf-san. However, The timing of a
> release was different. Then, patch is only current CVS-HEAD.
> http://cvs.ossp.org/chngview?cn=6001
>
> I thought that this problem was very important. It was sufficient reason to
> apply to 8.3.3 of pginstaller. Therefore, It should return the result of a
> wish.

It's not in 8.3.3 - I'm still waiting for details of how to build it,
as it's not exactly obvious.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [pgsql-es-ayuda] Copia y restauracion de base de datos de GForge

Restaurando la copia de la BBDD de
/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql
SET
SET
SET
SET
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:13:
ERROR: no existe la restricción «wikipageid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:14:
ERROR: no existe la restricción «userprojectid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:15:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:16:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:17:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:18:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:19:
ERROR: no existe la relación «public.users_idx»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:20:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:21:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:22:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:23:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:24:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:25:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:26:
ERROR: no existe la restricción «userid_fk»
psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:27:
ERROR: no existe la restricción «userid_fk»

Eso es lo primero que saca, como ves, no parece que de ninguno acerca de copy...

2008/6/13, Alvaro Herrera <alvherre@alvh.no-ip.org>:
> Clemente López Giner escribió:
>> Para crear la copia de la bbdd lo he hecho con pg_dump:
>> pg_dump -c -v -f $ARCHIVEROOT/$INCREMENTDIR/$BACKUP_BBDD -U $USERNAME
>> $DBNAME
>> Y para restaurarla, con:
>> psql -f $ARCHIVEROOT/$INCREMENTDIR/$BACKUP_BBDD -d $DBNAME -U $USERNAME
>>
>> Pero nada, me sigue dando errores
>>
>> Algunos errores al restaurarlo (me da muchos):
>> psql:/backup/diarias/GForge/backup_13-06-2008/bbdd_GForge_13-06-2008.sql:32134:
>> ERROR: error de sintaxis en o cerca de «1» en el carácter 1
>
> [...]
>
> Debe haber errores antes que esos. Por favor muestra los primeros
> errores que da. Tiene que haber uno sobre falla de la orden COPY, antes
> que este error de sintaxis.
>
> PD: por favor no te olvides de copiar la lista.
>
> --
> Alvaro Herrera
> http://www.PlanetPostgreSQL.org/
> "En el principio del tiempo era el desencanto. Y era la desolación. Y era
> grande el escándalo, y el destello de monitores y el crujir de teclas."
> ("Sean los Pájaros Pulentios", Daniel Correa)
>
--
TIP 1: para suscribirte y desuscribirte, visita http://archives.postgresql.org/pgsql-es-ayuda