Hello,
I've just upgraded my database from 9.2.2 to 9.3.0 using pg_upgrade.
Besides I've updated hstore extension ("alter extension hstore update").
But I can't find new to 9.2 hstore functions such as "hstore_to_json" in my
database.
I found out that file "contrib/hstore/hstore.control" of pg 9.
Okay. I guess so. Thanks for your help.
Regards,
Payal
On Fri, Jul 6, 2012 at 4:24 PM, Bruce Momjian wrote:
> On Fri, Jul 06, 2012 at 04:21:06PM -0400, Payal Singh wrote:
> > If something was wrong with the cluster, why did vacuumdb on new server
> run
> > successfully when I followed Craig's s
On Fri, Jul 06, 2012 at 04:21:06PM -0400, Payal Singh wrote:
> If something was wrong with the cluster, why did vacuumdb on new server run
> successfully when I followed Craig's suggestion of running vacuumdb on old
> server first, before performing the upgrade, and then ran vacuumdb on new one?
M
If something was wrong with the cluster, why did vacuumdb on new server run
successfully when I followed Craig's suggestion of running vacuumdb on old
server first, before performing the upgrade, and then ran vacuumdb on new
one?
On Fri, Jul 6, 2012 at 4:05 PM, Bruce Momjian wrote:
> On Fri, Jul
On Fri, Jul 06, 2012 at 04:03:38PM -0400, Payal Singh wrote:
> The omnipitr-backup-slave process takes online backups from the standby, and
> this is done everyday. This process connects to the master and calls a
> pg_start_backup and then looks for a restore point on the standby after that
> WAL a
The omnipitr-backup-slave process takes online backups from the standby,
and this is done everyday. This process connects to the master and calls a
pg_start_backup and then looks for a restore point on the standby after
that WAL address. So i don't think I need to shut down the server.
Also, it is
On Fri, Jul 06, 2012 at 02:22:28PM -0400, Payal Singh wrote:
> The first message in the log is probably because the backup is taken from a
> standby. I am using omnipitr-backup-slave to make the backups and then
> restoring one of those.
OK, this is what I wanted to see. Is the server running whi
On Fri, Jul 06, 2012 at 01:20:21PM -0400, Payal Singh wrote:
> Hi,
>
> I restored the backup on 9.1, made sure the database reached a consistent
> state
> and checkpointed. Then I performed the upgrade. Upgrade completed successfully
> but on running vacuumdb it gave the exact same error. The con
On Thu, Jul 05, 2012 at 06:28:31PM -0400, Tom Lane wrote:
> Payal Singh writes:
> > On Thu, Jul 5, 2012 at 12:15 PM, Craig Ringer wrote:
> >> If you start 9.1 on a copy of the backup then cleanly stop it again, does
> >> pg_upgrade then run?
>
> > Thank you. That worked.
>
> ISTM that pg_upgrad
Payal Singh writes:
> On Thu, Jul 5, 2012 at 12:15 PM, Craig Ringer wrote:
>> If you start 9.1 on a copy of the backup then cleanly stop it again, does
>> pg_upgrade then run?
> Thank you. That worked.
ISTM that pg_upgrade should check that the old cluster was shut down
cleanly, ie pg_control h
Thank you. That worked.
Regards
Payal
On Thu, Jul 5, 2012 at 12:15 PM, Craig Ringer wrote:
> On 07/05/2012 11:20 PM, Payal Singh wrote:
>
> Hello,
>
> I am trying to use pg_upgrade to upgrade data from 9.1.4 to 9.2beta2.
> Although the upgrade completed successfully, vacuumdb --all --analyze
On 07/05/2012 11:20 PM, Payal Singh wrote:
Hello,
I am trying to use pg_upgrade to upgrade data from 9.1.4 to 9.2beta2.
Although the upgrade completed successfully, vacuumdb --all
--analyze-only gives an error. I tried upgrading two binary backups of
the same production database from differen
Hello,
I am trying to use pg_upgrade to upgrade data from 9.1.4 to 9.2beta2.
Although the upgrade completed successfully, vacuumdb --all --analyze-only
gives an error. I tried upgrading two binary backups of the same production
database from different days, and both returned the exact same error
Hi,
What platform? What does the server log says? Please refer to
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems for reporting
issues.
On Thu, May 17, 2012 at 11:52 AM, Karthik Ramasamy S <
karthik.ramas...@bahwancybertek.com> wrote:
> Hi All,
>
>
>
> We currently installed the po
Hi All,
We currently installed the postgre database 8.3 version.
We are trying to connect to the database after installation.
At first time its working fine but after any shutdown or any restart needed
for the particular machine, we are not able to connect the postgre server.
Initially we ins
On Fri, Mar 11, 2011 at 9:31 AM, Bruce Momjian wrote:
> Robert Haas wrote:
>> On Thu, Mar 10, 2011 at 10:37 PM, Bruce Momjian wrote:
>> > Robert Haas wrote:
>> >> On Thu, Mar 10, 2011 at 4:08 PM, Bruce Momjian wrote:
>> >> > Was this fixed?
>> >>
>> >> Not yet. ?I can probably fix it, if nobody
Robert Haas wrote:
> On Thu, Mar 10, 2011 at 10:37 PM, Bruce Momjian wrote:
> > Robert Haas wrote:
> >> On Thu, Mar 10, 2011 at 4:08 PM, Bruce Momjian wrote:
> >> > Was this fixed?
> >>
> >> Not yet. ?I can probably fix it, if nobody else wants to do it.
> >
> > Well, it has languished for five m
On Thu, Mar 10, 2011 at 10:37 PM, Bruce Momjian wrote:
> Robert Haas wrote:
>> On Thu, Mar 10, 2011 at 4:08 PM, Bruce Momjian wrote:
>> > Was this fixed?
>>
>> Not yet. I can probably fix it, if nobody else wants to do it.
>
> Well, it has languished for five months, so the "nobody else wants" p
Robert Haas wrote:
> On Thu, Mar 10, 2011 at 4:08 PM, Bruce Momjian wrote:
> > Was this fixed?
>
> Not yet. I can probably fix it, if nobody else wants to do it.
Well, it has languished for five months, so the "nobody else wants" part
is probably accurate. ;-)
--
Bruce Momjian htt
On Thu, Mar 10, 2011 at 4:08 PM, Bruce Momjian wrote:
> Was this fixed?
Not yet. I can probably fix it, if nobody else wants to do it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To
Was this fixed?
---
Alvaro Herrera wrote:
> Excerpts from Alvaro Herrera's message of jue nov 18 15:31:16 -0300 2010:
> > Excerpts from Robert Haas's message of jue nov 18 15:11:37 -0300 2010:
> >
> > > In the current maste
Hi,
I've tried everyting to install PostgreSQL, but I just can't make it work. I've
tried different versions, I've played with the settings of my firewall and did
basicly everything I've seen on the internet to fix it.
I'd like to ask if somebody can help me through teamviewer, cause I'm
def
On Thu, Nov 18, 2010 at 1:35 PM, Alvaro Herrera
wrote:
> Excerpts from Alvaro Herrera's message of jue nov 18 15:31:16 -0300 2010:
>> Excerpts from Robert Haas's message of jue nov 18 15:11:37 -0300 2010:
>>
>> > In the current master branch, it appears that "ALTER TABLE c INHERIT
>> > p" takes a
Hello Sir/Madam,
I am unable to install Postgresql "*Installer version Version 9.0.3-1
winx86-64" on my HP 64 bit laptop dv6000 series having Windows Vista OS.*
*
*
*As soon as I try to run executable file for installing postgresql , the
program aborts from inbetween and installation is cancelle
Excerpts from Alvaro Herrera's message of jue nov 18 15:31:16 -0300 2010:
> Excerpts from Robert Haas's message of jue nov 18 15:11:37 -0300 2010:
>
> > In the current master branch, it appears that "ALTER TABLE c INHERIT
> > p" takes a ShareUpdateExclusiveLock on the child, which seems
> > suffic
Excerpts from Robert Haas's message of jue nov 18 15:11:37 -0300 2010:
> In the current master branch, it appears that "ALTER TABLE c INHERIT
> p" takes a ShareUpdateExclusiveLock on the child, which seems
> sufficient, and an AccessShareLock on the parent, which seems like it
> might not be; thou
On Thu, Nov 18, 2010 at 10:28 AM, Jon Nelson wrote:
> On Wed, Nov 17, 2010 at 8:57 PM, Robert Haas wrote:
>> On Tue, Nov 16, 2010 at 10:48 AM, Jon Nelson
>> wrote:
>>> I have a process which runs in parallel creating tables which, as the
>>> /final/ step in the import, gets SQL much like the fo
On Wed, Nov 17, 2010 at 8:57 PM, Robert Haas wrote:
> On Tue, Nov 16, 2010 at 10:48 AM, Jon Nelson
> wrote:
>> I have a process which runs in parallel creating tables which, as the
>> /final/ step in the import, gets SQL much like the following applied:
>>
>> ALTER TABLE foo INHERIT bar;
>>
>> P
On Tue, Nov 16, 2010 at 10:48 AM, Jon Nelson wrote:
> I have a process which runs in parallel creating tables which, as the
> /final/ step in the import, gets SQL much like the following applied:
>
> ALTER TABLE foo INHERIT bar;
>
> Periodically, I get this error: tuple concurrently updated
>
> O
I have a process which runs in parallel creating tables which, as the
/final/ step in the import, gets SQL much like the following applied:
ALTER TABLE foo INHERIT bar;
Periodically, I get this error: tuple concurrently updated
Of course, I googled for the error message and see a bunch of issue
On 10/16/2010 08:58 PM, Robert Haas wrote:
2010/10/13 Sergey Burladyan:
IMHO you can receive question-marks here if lc_messages in postgresql.conf
do not match with locale from environment at server start, for example:
correctly translated and displayed:
$ LANG=ru_RU.UTF-8 ../bin/postgres -D d
On 4/04/2010 7:03 PM, Cedric CHAUVET wrote:
Hi
I had v8.3.0 and tried to upgrade it to v8.3.9-1.
I download and unzip. Then I double click on UPGRADE.bat.
During the installation, it stopped and pop up a window where it's written:
"An error occured during the installation of
assembly'policy.8.0.
Hi
I had v8.3.0 and tried to upgrade it to v8.3.9-1.
I download and unzip. Then I double click on UPGRADE.bat.
During the installation, it stopped and pop up a window where it's written:
"An error occured during the installation of
assembly'policy.8.0.Microsoft.VC80.CRT,publicKeyToken="1fc
p...@onet.eu writes:
> 2010-01-27 10:34:01 CET [3931]: [9-1] host=,user=,db= LOG: server process
> (PID 24454) was terminated by signal 11: Segmentation fault
> I have 8.4.0 version.
The *first* thing to do is update to 8.4.2 to see if the problem was
already fixed.
If not, you need to try to
Hello,
I've got problem with PostgreSQL crash (today it was twice).
Usually, average load5 is about 16-20. Today I've run new application and load
has increased dramatically.
First time before crash load was fast rising from 30 to 70 (log below)
2010-01-27 10:34:01 CET [3931]: [9-1] host=,user=,
On Mon, Sep 21, 2009 at 3:23 PM, Christine Penner
wrote:
> At 11:57 AM 21/09/2009, you wrote:
>>
>> What error you get when you run initdb?? (Also what exact command you
>> run?)
>
> The first time I just double clicked on the file initdb.exe. Just now I
> tried to run it through the command promp
At 11:57 AM 21/09/2009, you wrote:
What error you get when you run initdb?? (Also what exact command you run?)
The first time I just double clicked on the file initdb.exe. Just now
I tried to run it through the command prompt and go this, this is the
same stuff that was in the log file in the
On 09/21/2009 08:31 PM, Christine Penner wrote:
Hi,
I posted the following message to the General list a while ago. I am
still not able to run postgres at all.
I am trying to install Postgres 8.4. I had 8.3 installed. Because
I didn't have any important data, to make it easier I remo
Hi,
I posted the following message to the General list a while ago. I am
still not able to run postgres at all.
I am trying to install Postgres 8.4. I had 8.3 installed. Because I
didn't have any important data, to make it easier I removed 8.3, the data
directory, removed the Postgres windows u
Hello,
I would like to install postgreSQL in silent mode.I have gone through the link
http://pginstaller.projects.postgresql.org/silent.html and got to know the
options to install it but i am not successful. I have tried the following
command with lot of options.
msiexec
/i "Z:\postgresql\pos
"Merlin Moncure" writes:
> I _may_ have found a problem that is affecting non-greedy regex matches.
No, you didn't read the fine print in section 9.7.3.5; particularly
A branch -- that is, an RE that has no top-level | operator -- has the
same greediness as the first quantified atom in i
I _may_ have found a problem that is affecting non-greedy regex matches.
select regexp_matches(
$$x = foo y x = foo y $$,
$$x\s+(.*?)y$$ ,'g');
As I read it, this should match ' = foo' twice. Instead, it matches
"= foo y x = foo " once. The non-greedy form (.*?) should break out
at the fir
2009/1/5 Tomáš Dixa :
> Hello,
>
>
>
> I have problem with instalation on step 8 (on PostgreSQL Setup
> Instructions)-
>
> Initial database cluster.
>
>
>
> It´s written there – The Postere SQL data direktory must be on an NTFS
> formatted volume. If you wish
>
> to install the data direktory on an
Hello,
I have problem with instalation on step 8 (on PostgreSQL Setup
Instructions)-
Initial database cluster.
It´s written there - The Postere SQL data direktory must be on an NTFS
formatted volume. If you wish
to install the data direktory on another type of partition you must
initiali
lftsang wrote:
> Dear Sir,
>
> I tried to install PostgreSQL 8.1.15 on Freebsd 7.0. When I extracted
> the .tar.gz and inputed 'make' it shows the following error:
Did you try gmake?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulti
lftsang writes:
> I tried to install PostgreSQL 8.1.15 on Freebsd 7.0. When I extracted
> the .tar.gz and inputed 'make' it shows the following error:
> "/usr/share/mk/bsd.port.mk", line 11: Could not find
> /usr/ports/Mk/bsd.port.mk
> "Makefile", line 177: Malformed conditional (${ARCH} == spa
lftsang wrote:
Dear Sir,
I tried to install PostgreSQL 8.1.15 on Freebsd 7.0. When I extracted
the .tar.gz and inputed 'make' it shows the following error:
"/usr/share/mk/bsd.port.mk", line 11: Could not find
/usr/ports/Mk/bsd.port.mk
"Makefile", line 177: Malformed conditional (${ARCH} == s
Dear Sir,
I tried to install PostgreSQL 8.1.15 on Freebsd 7.0. When I extracted
the .tar.gz and inputed 'make' it shows the following error:
"/usr/share/mk/bsd.port.mk", line 11: Could not find
/usr/ports/Mk/bsd.port.mk
"Makefile", line 177: Malformed conditional (${ARCH} == sparc64 &&
${OSV
Martin Gregorie <[EMAIL PROTECTED]> writes:
> For some reason, when my message table (see below) is dumped, blank
> lines are introduced between rows.
Nothing like that has been reported before. We have heard of dump files
getting corrupted after they've been produced --- the most common case
is
Guys,
I apologise for sending a bug report this way, but the bug reporting
server seems to be out to lunch at present. Firefox reports being able
to contact it but its bug submission wasn't accepted. To avoid loss of
the bug report, here it is:
Name: Martin Gregorie
e-mail: [EM
[EMAIL PROTECTED] wrote:
> select ats.id, ap.value from akh_test_suit ats
> LEFT JOIN akh_properties ap on ap.ID = ats.test_suit_type_id
> where ats.ID = 472
>
> id | value
> 472 | 472
> ID -- integer
> value -- text
>
>
> select * from akh_test_suit ats
> LEFT JOIN akh_properties ap on ap.ID
nt: Tuesday, August 26, 2008 1:15 PM
Subject: Re: [BUGS] Problem with planer
[EMAIL PROTECTED] wrote:
select ats.id, ap.value from akh_test_suit ats
LEFT JOIN akh_properties ap on ap.ID = ats.test_suit_type_id
where ats.ID = 472
id | value
472 | 472
ID -- integer
value -- text
select * from akh_t
[EMAIL PROTECTED] wrote:
select ats.id, ap.value from akh_test_suit ats
LEFT JOIN akh_properties ap on ap.ID = ats.test_suit_type_id
where ats.ID = 472
id | value
472 | 472
ID -- integer
value -- text
select * from akh_test_suit ats
LEFT JOIN akh_properties ap on ap.ID = ats.test_suit_type_id
whe
select ats.id, ap.value from akh_test_suit ats
LEFT JOIN akh_properties ap on ap.ID = ats.test_suit_type_id
where ats.ID = 472
id | value
472 | 472
ID -- integer
value -- text
select * from akh_test_suit ats
LEFT JOIN akh_properties ap on ap.ID = ats.test_suit_type_id
where ats.ID = 472 and ap.v
flag *D:# dй: dйfaire, dйgrossir
. > dй
flag *N:# йlision d'une nйgation
[aавeийкiоoфuh] > n' # je n'aime pas, il n'y a pas
---
"Jean-Baptiste Quenot" <[EMAIL PROTECTED]> writes:
> I'm having problem with french dictionaries. Loading an ispell affix
> file with apostrophes does not work. The file comes from the ifrench
> (french dict for ispell) debian source package at
> http://packages.debian.org/sid/ifrench
> dockee=#
I'm having problem with french dictionaries. Loading an ispell affix
file with apostrophes does not work. The file comes from the ifrench
(french dict for ispell) debian source package at
http://packages.debian.org/sid/ifrench
Here's the session excerpt:
shohorab hossain wrote:
Dear sir/madam,
This is to inform you that I am an oracle database user/administrator. But I am
going to join in a company where I have to administrate postgresql database. I
am new to this database system. For few days I am trying to install
postgresql-8.3.1 in RHEL4
Dear sir/madam,
This is to inform you that I am an oracle database user/administrator. But I am
going to join in a company where I have to administrate postgresql database. I
am new to this database system. For few days I am trying to install
postgresql-8.3.1 in RHEL4. My machine configuration
Dear sir/madam,
This is to inform you that I am an oracle database user/administrator. But I am
going to join in a company where I have to administrate postgresql database. I
am new to this database system. For few days I am trying to install
postgresql-8.3.1 in RHEL4. My machine configuration
Dear sir/madam,
This is to inform you that I am an oracle database user/administrator. But I am
going to join in a company where I have to administrate postgresql database. I
am new to this database system. For few days I am trying to install
postgresql-8.3.1 in RHEL4. My machine configuration
=?iso-8859-2?Q?Wojciech_Strza=B3ka?= <[EMAIL PROTECTED]> writes:
>> To make that happen would require (at least) a full table scan. I think
>> most people are more interested in DROP COLUMN being a cheap operation
>> than in having the space be reclaimed quickly.
>> For a comparison point: large
> To make that happen would require (at least) a full table scan. I think
> most people are more interested in DROP COLUMN being a cheap operation
> than in having the space be reclaimed quickly.
> For a comparison point: large field values that don't happen to get
> toasted don't vanish immedia
=?iso-8859-2?Q?Wojciech_Strza=B3ka?= <[EMAIL PROTECTED]> writes:
> In my opinion the fact that dropping column doesn't release it's toastable
> resources is a bug.
To make that happen would require (at least) a full table scan. I think
most people are more interested in DROP COLUMN being a cheap
I've found some strange behavoiur of TOAST'able tables.
1. Lets create table with toastable column
CREATE table toastable (
x int ,
y text
);
2. Check toast size - as the table is empty it's size 0 - OK
SELECT relname, pg_relation_size(oid) FROM pg_class where oid=(select
reltoastrelid from
The first record ctid=(0,1) is obsolete, you can delete it. It is probably race
condition in VACUUM and catalog modification. Did you added or modified any user
account (e.g. password change) in related time? Please, can you let us know
exact version of PostgreSQL?
Zdenek
Kho
Hello, help me please,
I don't know how, but i got 2 postgres users.
How can I delete the first one
thx alot for your answers.
///
select passwd,ctid,
Hi Alvaro
On Fri, Mar 28, 2008 at 6:05 PM, Alvaro Herrera <[EMAIL PROTECTED]>
wrote:
> NikhilS escribió:
>
> > I will take a look at the pg_dump related changes if you want. We will
> need
> > changes in flagInhAttrs() and in getTableAttrs() to query the backend
> for
> > these 2 attributes for p
On Fri, Mar 28, 2008 at 4:07 AM, NikhilS <[EMAIL PROTECTED]> wrote:
> Hi Alex,
>
>
> On Fri, Mar 28, 2008 at 4:58 AM, Alex Hunsaker <[EMAIL PROTECTED]> wrote:
> > Attached is a WIP patch I have been playing with in my spare time. It
> > should take care of the first 2. It does nothing for pg_dump
NikhilS escribió:
> P.S Alvaro, I think this patch did not reach the mailing list and was
> stalled due to size restrictions or something.
OK, it's archived now:
http://archives.postgresql.org/pgsql-patches/2008-03/msg00392.php
Thanks.
--
Alvaro Herrerahttp://www
NikhilS escribió:
> P.S Alvaro, I think this patch did not reach the mailing list and was
> stalled due to size restrictions or something.
Argh, you are right. We don't have this on the archives anywhere :-(
Probably it got stuck on Maia ...
--
Alvaro Herrerahtt
Hi Alex,
On Fri, Mar 28, 2008 at 4:58 AM, Alex Hunsaker <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 27, 2008 at 5:14 AM, NikhilS <[EMAIL PROTECTED]> wrote:
> > * Add logic to disallow ADD CONSTRAINT ONLY to parent of an inheritance
> > hierarchy
> >
> > * Add logic to mark inherited constraints in t
I am installing 8.1.4 on a Windows XP SP2 virtual machine (VMWare). It seems
that if I specify BASEDIR= in my command line, and is NOT the
default install path, I get the error "internal account lookup failure"
immediately after the postgres user account is created. If I leave the
BASEDIR stateme
NikhilS <[EMAIL PROTECTED]> writes:
> ...
> * Add logic to mark inherited constraints in the children:
> This can be achieved by introducing a new bool "coninherited" attribute in
> pg_constraint. This will be set to true on only those check constraints that
> are added to children via the inherita
NikhilS wrote:
Am important decision here is about adding a new attribute to pg_constraint
as it is the only sane way of determining inherited constraints, but that
will require an initdb. Comments?
There's no problem forcing an initdb at this point in the release cycle.
We will do that for su
Hi,
On Thu, Mar 20, 2008 at 7:36 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> More to the point, it takes a capability away from the user without
> actually solving the problem we need to solve, namely to guarantee
> consistency between parent and child constraints. You can be sure
> that there i
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> NikhilS escribió:
>> Ok, I understand. But even then this could patch could be considered even if
>> it does not solve the TODO completely, no? It atleast disallows ONLY ADD
>> CONSTRAINT on the parent.
> No, because you would then feel that the TODO it
Hi,
On Thu, Mar 20, 2008 at 6:11 PM, Alvaro Herrera <[EMAIL PROTECTED]>
wrote:
> NikhilS escribió:
>
> > On Wed, Mar 19, 2008 at 8:23 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> > > If it's a small patch, it's wrong by definition. AFAICS there is no
> way
> > > to fix this correctly that doesn't
NikhilS escribió:
> On Wed, Mar 19, 2008 at 8:23 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> > If it's a small patch, it's wrong by definition. AFAICS there is no way
> > to fix this correctly that doesn't involve catalog changes. The point
> > of the TODO is that you have to enforce that the inh
Hi,
On Wed, Mar 19, 2008 at 8:23 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> NikhilS <[EMAIL PROTECTED]> writes:
> > On Fri, Mar 7, 2008 at 6:37 AM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> >> Added to TODO:
> >> o Require all CHECK constraints to be inherited
>
> > PFA, a small patch attached wh
NikhilS <[EMAIL PROTECTED]> writes:
> On Fri, Mar 7, 2008 at 6:37 AM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>> Added to TODO:
>> o Require all CHECK constraints to be inherited
> PFA, a small patch attached which should fix this.
If it's a small patch, it's wrong by definition. AFAICS there i
Hi,
On Fri, Mar 7, 2008 at 6:37 AM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> Added to TODO:
>
> > o Require all CHECK constraints to be inherited
> >
> > http://archives.postgresql.org/pgsql-bugs/2007-04/msg00026.php
>
>
PFA, a small patch attached which should fix this. I have
Remove the "docs" feature from ADDLOCAL. This will prevent error 2711
(installation package could not be opened).
I also had problems using the SERVICEDOMAIN="%COMPUTERNAME% argument - it
seems to cause MSI to report errors 1708 and 1709 and aborts the
installation.
divya shree wrote:
>
> hi
Added to TODO:
> o Require all CHECK constraints to be inherited
>
> http://archives.postgresql.org/pgsql-bugs/2007-04/msg00026.php
---
Tom Lane wrote:
> "Chris Fischer" <[EMAIL PROTECTED]> writes:
> > alter
hi,
when i try silent installation of postgres using the example in
your website msiexec /i postgresql-8.0.0-rc1-int.msi /qr INTERNALLAUNCH=1
ADDLOCAL=server,psql,docs SERVICEDOMAIN="%COMPUTERNAME%"
SERVICEPASSWORD="SecretWindowsPassword123" SUPERPASSWORD="VerySecret"
Andrew Shea <[EMAIL PROTECTED]> writes:
> However the following code doesn't work even though it is very similar
> to the first query (that is, and aggregate function within a case
> statement):
> select (SELECT CASE WHEN (1=2) THEN 0 ELSE COUNT(*) END) from (
^^
> select 1 as cou
On Fri, 11 May 2007 14:47:04 +1000, Andrew Shea <[EMAIL PROTECTED]> wrote:
> The following works as expected:
>
> select (SELECT CASE WHEN (1=2) THEN 0 ELSE sum(count) END) from (
> select 1 as count union select 2 union select 3
> ) as "temp";
>
> The result is "6".
>
> The following also work
The following works as expected:
select (SELECT CASE WHEN (1=2) THEN 0 ELSE sum(count) END) from (
select 1 as count union select 2 union select 3
) as "temp";
The result is "6".
The following also works as expected:
select count(*) from (
select 1 as count union select 2 union select 3
) as "
"Chris Fischer" <[EMAIL PROTECTED]> writes:
> alter table only t1 add constraint ck_col1 check (number <> 0);
The bug here is that we allow that. Continuing your example,
regression=# insert into t2 values(0);
INSERT 0 1
regression=# select * from t1;
col1
--
0
(1 row)
which sure looks
There's no way in the pg_ tables to identify when a check constraint on
an inherited table should not be inherited. Example:
create table t1 (col1 number(10));
create table t2 () inherits t2;
alter table only t1 add constraint ck_col1 check (number <> 0);
Now, run pg_dump and notice that t
Hello,We have a Postgresql 8.1.8 and a problem, probably no bug.But we must go in production tomorrow and we don't know where to look to solve this. Therefore I hope somebody can help us.The problem is when we insert with a function, we get the message SQLSTATE = 25P02Error while executing the quer
Rob Schall <[EMAIL PROTECTED]> writes:
> I have to queries. One runs in about 2 seconds. The other takes upwards
> of 2 minutes. I have a temp table that is created with 2 columns. This
> table is joined with the larger database of call detail records.
> However, these 2 queries are handled very di
Question for anyone...
I have to queries. One runs in about 2 seconds. The other takes upwards
of 2 minutes. I have a temp table that is created with 2 columns. This
table is joined with the larger database of call detail records.
However, these 2 queries are handled very differently.
The queries
I’m installing postgresql
in a O.S. Linux Ubuntu 6.06 and I have the next printout at installation
process:
Setting up postgresql-7.4
(7.4.12-3) ...
Error: cluster configuration
already exists
I can’t find information about how I can solve the
problem
Adam <[EMAIL PROTECTED]> writes:
> The 'configure --enable-thread-safety' script fails when CFLAGS
> contain "-mcpu=7400", "-mcpu=970" or "-maltivec".
This has been discussed before, and the conclusion was "don't do that".
http://archives.postgresql.org/pgsql-hackers/2005-11/msg00104.php
> I w
Adam wrote:
> Greetings,
>
> There is a problem with PostgreSQL 8.1.4 on Mac OS X (PowerPC).
>
> The 'configure --enable-thread-safety' script fails when CFLAGS
> contain "-mcpu=7400", "-mcpu=970" or "-maltivec". With these flags,
> the GCC compiler enables AltiVec instructions for the PowerP
Greetings,
There is a problem with PostgreSQL 8.1.4 on Mac OS X (PowerPC).
The 'configure --enable-thread-safety' script fails when CFLAGS
contain "-mcpu=7400", "-mcpu=970" or "-maltivec". With these flags,
the GCC compiler enables AltiVec instructions for the PowerPC
processor, and define
Tom Lane wrote:
> julien <[EMAIL PROTECTED]> writes:
> > The INSTALL file mention the command "kill `cat
> > /usr/local/pgsql/data/postmaster.pid`" but the pid file contain the pid
> > but not only, it also contain data directory and some numbers (memory
> > usage ?, database characteristic ?)
>
julien <[EMAIL PROTECTED]> writes:
> The INSTALL file mention the command "kill `cat
> /usr/local/pgsql/data/postmaster.pid`" but the pid file contain the pid
> but not only, it also contain data directory and some numbers (memory
> usage ?, database characteristic ?)
Hm, I wonder why this docu
Hello,
I'm posted a short modification of the kill command.
The INSTALL file mention the command "kill `cat
/usr/local/pgsql/data/postmaster.pid`" but the pid file contain the pid
but not only, it also contain data directory and some numbers (memory
usage ?, database characteristic ?)
So wh
1 - 100 of 366 matches
Mail list logo
