=?ISO-8859-1?Q?L=E1szl=F3_Lajos_J=E1nszky?= writes:
> The following query returns nothing, but it should return 1.
> *SELECT 1 FROM NOT(ARRAY[1] <@ NULL**); *
I assume you meant SELECT 1 WHERE NOT(ARRAY[1] <@ NULL) ?
Because what you wrote doesn't parse.
This is not a bug. "ARRAY[1] <@ NULL" y
On Thu, Jul 18, 2013 at 10:52 AM, Michael Kunzmann wrote:
> Am 18.07.2013 17:33, schrieb bricklen:
>
>
> On Wed, Jul 17, 2013 at 10:46 PM, Michael Kunzmann <
> m...@michaelkunzmann.com> wrote:
>
>>
>> I've noticed the following issue when autostarting PostgreSQL under
>> Ubuntu 12.04 64bit by bo
On Wed, Jul 17, 2013 at 10:46 PM, Michael Kunzmann wrote:
>
> I've noticed the following issue when autostarting PostgreSQL under
> Ubuntu 12.04 64bit by bootup. I'm using PostgreSQL 9.1.
>
> 2013-07-18 06:44:12 CEST FATAL: could not create shared memory segment:
>
How much RAM do you have, and
Michael Kunzmann wrote
> Hello,
>
> I've noticed the following issue when autostarting PostgreSQL under
> Ubuntu 12.04 64bit by bootup. I'm using PostgreSQL 9.1.
>
> A manual service start works (service postgresql start).
Not sure what you actually think is the bug...especially since PostgreSQL
On Thu, Nov 19, 2009 at 12:20 PM, Tom Lane wrote:
> I'm less sure about the 1-click installer. I suspect that a lot of the
> people filing bugs here couldn't really tell whether their problem is
> specific to the installer or not. In any case, some of the relevant
> EDB people (Dave Page for in
On Wed, 18 Nov 2009, Tom Lane wrote:
Robert Haas writes:
I see that there's been no response to bugs #5194, #5187, #5051.
Should we consider adding a message to the bug reporting page that
suggests emailing the relevant list directly for JDBC/ODBC bugs?
+1. Either that or somebody takes r
Robert Haas writes:
> I see that there's been no response to bugs #5194, #5187, #5051.
> Should we consider adding a message to the bug reporting page that
> suggests emailing the relevant list directly for JDBC/ODBC bugs?
+1. Either that or somebody takes responsibility for forwarding
bug repor
Thanks alot, log_statement = all shows where come the errors.
On 4 mai, 10:49, [EMAIL PROTECTED] (Heikki Linnakangas) wrote:
> DNS wrote:
> > Even desactivate Auto-vacuum didn't fix my issue. Is there any place
> > where I can see past transactions or transactions in queue that hasn't
> > been pro
DNS escribió:
> Even desactivate Auto-vacuum didn't fix my issue.
I don't think anybody ever suggested that autovacuum had something to do
with it.
> Is there any place
> where I can see past transactions or transactions in queue that hasn't
> been processed ?
Why are you bothering with investig
DNS wrote:
Even desactivate Auto-vacuum didn't fix my issue. Is there any place
where I can see past transactions or transactions in queue that hasn't
been processed ?
You could put log_statement = all to your postgresql.conf. That'll log
every statement sent to the server to the log file.
T
Even desactivate Auto-vacuum didn't fix my issue. Is there any place
where I can see past transactions or transactions in queue that hasn't
been processed ?
Thank you,
On 2 mai, 10:02, [EMAIL PROTECTED] (Alvaro Herrera) wrote:
> DNS escribió:
>
> > On 27 avr, 19:17, [EMAIL PROTECTED] (Tom Lane)
DNS escribió:
> On 27 avr, 19:17, [EMAIL PROTECTED] (Tom Lane) wrote:
>
> > This is just a warning, which most likely is there only because somebody
> > typed COMMIT or ABORT unnecessarily. What problem are you actually having?
>
> No one is working on the database when come up the warning. The
On 27 avr, 19:17, [EMAIL PROTECTED] (Tom Lane) wrote:
> This is just a warning, which most likely is there only because somebody
> typed COMMIT or ABORT unnecessarily. What problem are you actually having?
No one is working on the database when come up the warning. The
warning makes us worrier a
DNS <[EMAIL PROTECTED]> writes:
> 3- In pgsql log, I have this message:
> 2007-04-27 14:15:05 EDT user database WARNING: 25P01: there is no
> transaction in progress
This is just a warning, which most likely is there only because somebody
typed COMMIT or ABORT unnecessarily. What problem are yo
I forget to add, it's PGSQL version 8.1 . Thank you!
---(end of broadcast)---
TIP 6: explain analyze is your friend
[EMAIL PROTECTED] napsal(a):
Compiling PostgreSQL 8.1.4 under Solaris 10, I ran into a problem documented
back on 2006-05-30. Apparently in order to compile successfully, one has to
remove an unreferenced function pqsignalinquire() in
src/interfaces/libpq/pqsignal.c.
Since I stepped into th
Based on the date of the posting, I think this will be fixed when we
release 8.1.5 soon. If you want, use CVS to pull the 8_1 tag and try
that.
---
[EMAIL PROTECTED] wrote:
> Compiling PostgreSQL 8.1.4 under Solaris 10, I r
Robert Treat wrote:
> On Sunday 06 March 2005 15:25, Hashem Masoud wrote:
> > Hi,
> >
> > I think this is a typo in:
> > http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html
> >
> >
> > lfirst(i), lfirst_int(i), lfirst_oid(i)
> > return the data (a point, inteter and OID
> > respecti
Tom,
> the issue is clearly that the known-false HAVING clause is pushed down
> inside the aggregation, as though it were WHERE. ÂThe existing code
> pushes down HAVING to WHERE if the clause contains no aggregates, but
> evidently this is too simplistic. ÂWhat are the correct conditions for
> pus
On Monday 07 March 2005 16:22, Robert Treat wrote:
> On Sunday 06 March 2005 15:25, Hashem Masoud wrote:
> Thanks for the report! Attached patch fixes this and 3-4 other typos as
> well.
Hashem has kindly pointed out a few more typos in the FAQ that I have added
in, please apply this patch inste
On Sunday 06 March 2005 15:25, Hashem Masoud wrote:
> Hi,
>
> I think this is a typo in:
> http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html
>
>
> lfirst(i), lfirst_int(i), lfirst_oid(i)
> return the data (a point, inteter and OID
> respectively) at list element i.
>
>
> (inteter)
patch attached.
-- Forwarded Message --
Subject: [pgsql-www] Fw: typos in the docu
Date: Wednesday 02 March 2005 12:44
From: "Stefan Hans" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
- Original Message -
From: Stefan Hans
To: pgsql-bugs@postgresql.org
Sent: Wednesday,
Byron,
> PostgreSQL Âworks perfectly if the Win Xp does not have installed Service
> Pack, the problem occurs when Win Xp has Service Pack 1 or 2. ÂPostgreSQL
> does not activate Âor doesnât work Âand it presents this error:
The Windows XP services packs contain a built-in firewall which autmatic
Alexander,
> When I add a server in Windows XP with service pack Â1 or 2 always the
> connection is refused, but when I add a server in Windows XP without
> service pack, I do not have any problem, so, I would like know how I could
> solve this problem, or if this problem is with the S.O. or confi
Steve McWilliams wrote:
Nevermind, I found out what this was. Turned out that the customer
machine in question had particularly heavy security settings and so the
enetaware account did not have permission to write into the directory
where it was trying to create PGDATA. Once I widened the settin
"Steve McWilliams" <[EMAIL PROTECTED]> writes:
> Nevermind, I found out what this was. Turned out that the customer
> machine in question had particularly heavy security settings and so the
> enetaware account did not have permission to write into the directory
> where it was trying to create PGDA
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: 23 December 2004 15:30
> To: Kamp Kaibo Huang
> Cc: [EMAIL PROTECTED]; pgsql-bugs@postgresql.org
> Subject: Re: [pgsql-www] BUG #1356: pg_get_serial_sequence
> can not find a table
Found the problem...it's been reported before.
http://archives.postgresql.org/pgsql-bugs/2004-11/msg00195.php
I was a bad boy and left off the part about the missing ordinal in
libeay32.dll...
Dunno if that's something that still needs to be fixed, but at least
I've got a workaround.
Scott
-
I assume the script is broken..._I_ sure didn't send it to -www :)
No, no real lockdown except for the Windows Firewall that installs with
SP2, but it didn't complain or offer to block or unblock as usual. The
postgres account that it created was granted the 'logon as a service'
right, but I have
"Kamp Kaibo Huang" <[EMAIL PROTECTED]> writes:
> select pg_get_serial_sequence('tTestTableAnother','FId')
> ERROR: relation "ttesttableanother" does not exist
I think you need
select pg_get_serial_sequence('"tTestTableAnother"','"FId"');
regards, tom lane
[ could we ple
(um, why was this filed to -www? Copying over to -bugs where it should
be. Something wrong with the scripts, I assume)
> The following bug has been logged online:
>
> Bug reference: 1355
> Logged by: Scott Stillwell
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
Tom,
> We could adjust guc.c to limit checkpoint_segments to the range 1..255
> without having to touch any translatable strings. ÂThis isn't a
> necessary change but it seems harmless ... any objections?
+1 in favor.
We'll need to change the value in runtime-config.sgml and in pg_settings, too.
On Wed, Nov 17, 2004 at 11:53:10 -0800,
Josh Berkus <[EMAIL PROTECTED]> wrote:
> Karl,
>
> > I don't care that much about the behavior, it's easy enough
> > to delete 'public'. I do think that a note should be
> > made in the administrator manual regards system upgrades
> > where pg_dump(all) s
Karl,
> I don't care that much about the behavior, it's easy enough
> to delete 'public'. ÂI do think that a note should be
> made in the administrator manual regards system upgrades
> where pg_dump(all) scripts are given if this is going to be
> the behavior.
This isn't isolated to the "public"
Brendan,
> Description: Â Â Â Âupdate does not honor order of subselect
>
> Details:
>
> SQL Update command does not follow the order of a WHERE field IN subselect.
>
> In the following code, I try to reset the order of rows in a column by
> updating an order field. ÂUpdate does not honor the orde
Michael, Ralph, etc.:
> Rules are macros, so when you refer to NEW.storage_id in the rule
> then the default expression "nextval('tmp_storage_id_seq')" is
> evaluated again. ÂIf you don't want that to happen then use a
> trigger.
>
> This comes up often -- maybe somebody could add it to the FAQ.
OK, fixed.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > + /*
> > + * Escape any single quotes or backslashes in locale
> > + */
> > + static void
> > + escape_locale(char **locale)
> > + {
> > + in
Bruce Momjian <[EMAIL PROTECTED]> writes:
> + /*
> + * Escape any single quotes or backslashes in locale
> + */
> + static void
> + escape_locale(char **locale)
> + {
> + int len = strlen(*locale),
> + i, j;
> + char*loc_temp = x
I have reviewed your patch. I found that the first patch was definitely
needed. Your code adds escapes for single quotes in locale names placed
in postgresql.conf. I also added code to escape a literal backslash as
well. I re-factored your code and applied the attached patch.
Your second patc
I do not see a patch. Did you forget to attach it?
---
Zhong Jacky wrote:
> Hi pgsql-bugs,
>
>I'm a Chinese and I am using WinXp Chs to compile pgsql 8.0 beta 1
> in the MinGW environment. I found 2 bugs and fix them,
On Friday 20 August 2004 03:52, Tom Lane wrote:
> Stefanos Harhalakis <[EMAIL PROTECTED]> writes:
> > It seems that the problem is in src/template/linux:
> >
> > $ cat src/template/linux=20
> > # Force _GNU_SOURCE on; plperl is broken with Perl 5.8.0 otherwise
> > CPPFLAGS="-D_GNU_SOURCE"
> >
> > w
Stefanos Harhalakis <[EMAIL PROTECTED]> writes:
> It seems that the problem is in src/template/linux:
> $ cat src/template/linux=20
> # Force _GNU_SOURCE on; plperl is broken with Perl 5.8.0 otherwise
> CPPFLAGS="-D_GNU_SOURCE"
> which is beeing sourced by configure.in. Changing this to
> CPPFLAG
On Wednesday 18 August 2004 23:09, Peter Eisentraut wrote:
> Stefanos Harhalakis wrote:
> > This happens because AC_CHECK_HEADERSis implemented using the
> > preprocessor (cpp/gcc -E) without adding CFLAGS/CXXFLAGS:
>
> The correct variable is CPPFLAGS. Actually, you can also use
> --with-includes
On Wednesday 18 August 2004 20:14, Peter Eisentraut wrote:
> Stefanos Harhalakis wrote:
> > It seems that you've removed the possibility to add an argument to
> > --with-openssl option of the configure script. Currently I'm
> > maintaining two systems where the openssl is not somewhere in the
> >
Stefanos Harhalakis wrote:
> This happens because AC_CHECK_HEADERSis implemented using the
> preprocessor (cpp/gcc -E) without adding CFLAGS/CXXFLAGS:
The correct variable is CPPFLAGS. Actually, you can also use
--with-includes, but this is only in PostgreSQL, so I suggest you get
used to CPPFL
Stefanos Harhalakis wrote:
> It seems that you've removed the possibility to add an argument to
> --with-openssl option of the configure script. Currently I'm
> maintaining two systems where the openssl is not somewhere in the
> standard paths and thus the only way to compile with SSL seems to be
"Cavit Keskin" <[EMAIL PROTECTED]> writes:
> Postgresql often stops after a time (unknown, changing).
You haven't given any information that would allow anyone to help :-(
> Below is the log file just after Postgresql database server is started
> manually. Log can't record the cause of this probl
On Thursday 13 February 2003 05:06, Pablo Capeluto wrote:
> Your name : Pablo Capeluto
> Your email address : [EMAIL PROTECTED]
> Mi comando para correr PostgreSQL es rcpostgresql start, funciona bien,
> postgresql status me dice "runing" pero las aplicaciones que uso para
> hace
Currency is always going to depend on the cost of who you are buying it
from, no?
On Wed, 29 Jan 2003 14:14:02 +0100
[EMAIL PROTECTED] wrote:
>
> Come to think of it, even the point in time isn't enough (I remember
> times where you got more Deutsche Mark for an US dollar in the Soviet
> Union t
On Tue, Jan 28, 2003 at 17:47:14 -0500, tom lane wrote:
[...]
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > How would the new "money" be different from "numeric"?
>
> [ temporarily re-dons currency-trader hat... ]
>
> What would actually be useful is a money type that carries along an
> in
"Darko Prenosil" <[EMAIL PROTECTED]> writes:
> Here is changed fe-connect.c
Could we see a "diff -c" against what you started from, rather
than trying to intuit what changes you want to make?
regards, tom lane
---(end of broadcast)
> Non-Blocking Connection is not working under WIN32 build of PGSQL interface.
> I Spend some time to make it work.
> Here is changed fe-connect.c
>
> I did not check if all of non-blocking functions are working,
> but I checked PQsetnonblocking,PQisnonblocking,
> PQsendQuery, PQgetResult and fe
Tom,
Thanks for the quick response.
> Try it with the beta version's ODBC driver ...
How do I get it? I looked through the Development
version FTP filetree, and can't find the ODBC driver
anywhere. Link ... pretty please?
Second, I've also discovered that Pos
>> Try it with the beta version's ODBC driver ...
> How do I get it? I looked through the Development
> version FTP filetree, and can't find the ODBC driver
> anywhere. Link ... pretty please?
Darn if I know, I don't do Windows. Dave Page might have
a precompiled .dll available.
[EMAIL PROTECTED] writes:
> Windows 98 O.E.
> MS Access 97 SR 2a
> MDAC 2.5 and DCOM 98
> Postgres ODBC 6.50.00
^
> on two workstations.
> Postgres ODBC, whcih workes fine when the Postgres server runs 7.0.3,
> does not work when the server runs 7.1 beta 3.
Try it with the
long ago gone ... if you want to get on a list to post to, without being
swamped with email, send a 'subscribe-nomail' to the -request address for
the list ... especially great for those using news to post to the lists :)
On Wed, 17 Jan 2001, Jason Schroeder wrote:
> http://www.postgresql.org/
James Troup <[EMAIL PROTECTED]> writes:
> | template1=# create table x (y int4); insert into x values (31); select y,
>int4out(y) from x;
> | CREATE
> | INSERT 34029 1
> | y | int4out
> | +---
> | 31 | 136420312
> | (1 row)
The bug here is that the system allows you to inv
57 matches
Mail list logo
