unsubscribe
HI，你 用 过 网 易 相 册 批 量 上 传 工 具 吗 ？想 传 多 少 就 传 多 少 ，还 是 免 费 的！
Steven Mooij wrote:
> Some additional info. We repeated the test on different hardware with
> unfortunately the same result. This is the output of the postgresql
> logfile of that experiment:
[log messages about processes kill 9ed]
> This time we tested with postgresql 8.0.3 on a 2.6.12 linux ker
Duncan, do you have answers to any of these questions?
---
Magnus Hagander wrote:
> Wow, that's really weird :-)
>
> Do you have any pgpass.conf anywhere? Either on the local disk or on the
> network drive in question? Plea
On Tue, Jan 17, 2006 at 10:00:28PM +, Daniel Afonso Heisler wrote:
> When i run the following query, postgreSQL return TRUE.
> # SELECT true WHERE 1 NOT IN (2,3);
>
> But, when i run the next query, it don't return TRUE
> # SELECT true WHERE 1 NOT IN (2,NULL,3);
The expression "1 NOT IN (2,
"Gilles" <[EMAIL PROTECTED]> writes:
> When I configure in the file postgresql.conf:
> log_statement=mod
> I don't have the update, delete, insert queries logged like it says in the
> documentation :
> http://www.postgresql.org/docs/8.1/interactive/runtime-config-logging.html
Did you remember to d
Surya wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2184
> Logged by: Surya
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: Windows-2003 Server
> Description:Insertion problem
> Details:
>
> There is a probl
On 1/19/06, marc mamin <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2185
> Logged by: marc mamin
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1
> Operating system: DB Server: Linux Client: windows XP
> Description:
On Tue, 17 Jan 2006, Daniel Afonso Heisler wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2178
> Logged by: Daniel Afonso Heisler
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.X
> Operating system: Linux
> Description:NOT IN comm
varun bhasin wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2183
> Logged by: varun bhasin
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0
> Operating system: Windows Xp SP-1
> Description:Cannot enter Paragraph Type data
> Detail
On Wed, Jan 18, 2006 at 03:38:17PM +, Gilles wrote:
> When I configure in the file postgresql.conf:
> log_statement=mod
> I don't have the update, delete, insert queries logged like it says in the
> documentation :
> http://www.postgresql.org/docs/8.1/interactive/runtime-config-logging.html
>
We can't just throw away semicolons, e.g.:
\test=> \f ;
Field separator is ";".
The current behavior seems pretty good. It doesn't seem worth
improving.
---
Giles Morant wrote:
>
> The following bug has b
Anantha Prasad wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2182
> Logged by: Anantha Prasad
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.2-1
> Operating system: Win2000 Prof
> Description:Internal account lookup failure:
> D
Alexander Yeliseyev wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2186
> Logged by: Alexander Yeliseyev
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.2
> Operating system: SuSe Linux 9.2
> Description:syntax error in postgresql
The following bug has been logged online:
Bug reference: 2186
Logged by: Alexander Yeliseyev
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: SuSe Linux 9.2
Description:syntax error in postgresql.conf
Details:
[EMAIL PROTECTED]:~> ./pgSQL
The following bug has been logged online:
Bug reference: 2182
Logged by: Anantha Prasad
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2-1
Operating system: Win2000 Prof
Description:Internal account lookup failure:
Details:
I had not installed PostGreSQL o
The following bug has been logged online:
Bug reference: 2181
Logged by: Thomas Goerner
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: WinXP
Description:Bug in SQLNumResultCols
Details:
calling SQLNumResultCols on a hstmt that has been ex
The following bug has been logged online:
Bug reference: 2184
Logged by: Surya
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows-2003 Server
Description:Insertion problem
Details:
There is a problem when inserting a single quote in t
The following bug has been logged online:
Bug reference: 2185
Logged by: marc mamin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: DB Server: Linux Client: windows XP
Description:function compilation error with "Create [TEMP] table?
Details
The following bug has been logged online:
Bug reference: 2179
Logged by: stephanie
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: windows2000professional
Description:psql can't show chinese
Details:
The database encoding is EUC_CN. The
The following bug has been logged online:
Bug reference: 2180
Logged by: Gilles
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.0
Operating system: Linux RedHat ES3
Description:log_statement=mod does not work
Details:
When I configure in the file postgresql
The following bug has been logged online:
Bug reference: 2177
Logged by: Giles Morant
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.1
Operating system: Linux (Gentoo)
Description:(minor:) pgsql: Trailing semicolon on \d treated as
argument
Details:
When d
Tom Lane wrote:
"Steven Mooij" <[EMAIL PROTECTED]> writes:
testsearch=> insert into t_documentword2 (SELECT document_id,
t_word2.id,
frequency from t_documentword, t_word2 where t_documentword.word =
t_word2.word);
server closed the connection unexpectedly
There's not enough informati
The following bug has been logged online:
Bug reference: 2183
Logged by: varun bhasin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows Xp SP-1
Description:Cannot enter Paragraph Type data
Details:
I am trying to input a Resume in th
Hi.
I was trying to upgrade PostgreSQL from 7.2.8 to 8.1.2.
Dump and restore work well. But adddepend was failed.
To fix it, this regexp
$seq =~ s|^nextval\(["']+([^'"\)]+)["']+.*\)$|$1|g;
need to change
$seq =~ s|^nextval\(\(["']+([^'"\)]+)["']+.*\)$|$1|g;
or
$seq =~ s|^nextval\(\(?["']+([^'"\)]
Some additional info. We repeated the test on different hardware with
unfortunately the same result. This is the output of the postgresql
logfile of that experiment:
LOG: background writer process (PID 8208) was terminated by signal 9
LOG: terminating any other active server processes
LOG: s
The following bug has been logged online:
Bug reference: 2178
Logged by: Daniel Afonso Heisler
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.X
Operating system: Linux
Description:NOT IN command don't work
Details:
When i run the following query, postgreSQ
The following bug has been logged online:
Bug reference: 2176
Logged by: Francisco Leovey
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Linux
Description:Pgadmin III not honoring DATESTYLE
Details:
By default in postgresql.conf the DAT
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Chris Campbell wrote:
>> Do the stats need to persist across postmaster restarts (or crashes)?
> After a crash we forcibly _delete_ the stat file.
I'm not sure why, though --- the writing technique seems fairly safe,
and in any case the reader checks
> > In most cases you're going to see extremely few reads compared to
> > writes on pg_stats, right? So why not have the backends
> connect to the
> > stats process (or perhaps use UDP, or use the pipe, or
> whatever) and
> > fetch the data when needed. So when nobody fetches any
> data, ther
Sundaramoorthy, Annapoorani (Cognizant) wrote:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
Error while executing the query; ERROR: SELECT query has no destination
for result data
HINT: If you want to discard the results, use PERFORM instead.
This error is associated with the execut
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> In most cases you're going to see extremely few reads compared to writes
> on pg_stats, right? So why not have the backends connect to the stats
> process (or perhaps use UDP, or use the pipe, or whatever) and fetch the
> data when needed. So when nob
Chris Campbell wrote:
> On Jan 19, 2006, at 06:51, Magnus Hagander wrote:
>
> >In most cases you're going to see extremely few reads compared to
> >writes
> >on pg_stats, right? So why not have the backends connect to the stats
> >process (or perhaps use UDP, or use the pipe, or whatever) and
On Jan 19, 2006, at 06:51, Magnus Hagander wrote:
In most cases you're going to see extremely few reads compared to
writes
on pg_stats, right? So why not have the backends connect to the stats
process (or perhaps use UDP, or use the pipe, or whatever) and
fetch the
data when needed. So when
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Maybe the fact that the stat file is completely rewritten
> every 500 ms
> > should be reconsidered, if in the future someone chooses to rewrite
> > the stat system. We can reconsider this part then, as well.
>
> Yeah, it's becoming pretty obvio
34 matches
Mail list logo
