Dear All
Kindly guid us to export PostgreSQL Database from linux to windows.
Regards
Nitin
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Nitin Tarkar wrote:
Dear All
Kindly guid us to export PostgreSQL Database from linux to windows.
Nitin - this is not a bug, please post general questions to the
pgsql-general list (or -admin or -novice etc).
However, you should probably start by reading the section of the manuals
dealing w
On Fri, Sep 30, 2005 at 10:37:05PM -0500, Steve Peterson wrote:
> The query is submitted using the JDBC driver, via
> the SQLExplorer plugin for Eclipse.
>
> Is there a way for me to see the query as it was
> submitted to the backend? If so I'll take a look and see what it looks
> like.
Sure.
The following bug has been logged online:
Bug reference: 1936
Logged by: Alon Goldshuv
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8 (Current Dev)
Operating system: any
Description:Read-only transactions ignored in COPY
Details:
In the folllowing check (cop
select timestamp '2005-09-23 23:59:59.999'
I get the following result (note the value of the seconds):
2005-09-23 23:59:60.00
It's the leap second.
It is not a leap second. Leap seconds are always either on the 30th of
June or on the 31th of December.
Here there is a list of all t
Hi,
pg_stat_activity sometimes list no connections or a number of connections
much smaller than the number of postgres.exe processes.
We also have these messages in our PostgreSQL log approximately
20 times a day.
FATAL: could not read from statistics collector pipe: No error
FATAL: could not
The query is submitted using the JDBC driver, via
the SQLExplorer plugin for Eclipse.
Is there a way for me to see the query as it was
submitted to the backend? If so I'll take a look and see what it looks like.
S
At 09:58 AM 9/30/2005, Alvaro Herrera wrote:
On Thu, Sep 29, 2005 at 10:04:0
The following bug has been logged online:
Bug reference: 1937
Logged by: Tony Marston
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Windows XP
Description:Parts of information_schema only accessible to owner
Details:
I have been trying
On Tue, 4 Oct 2005, Tony Marston wrote:
> Description:Parts of information_schema only accessible to owner
> Details:
>
> I have been trying to access parts of the information_schema as an ordinary
> user, not as owner, and I am encountering instances where I cannot retrieve
> any rows at
Am Dienstag, 4. Oktober 2005 14:58 schrieb Tony Marston:
> As an example, in the view "information_schema.columns" I can only see the
> entry in COLUMN_DEFAULT if I am the owner. Why is this?
Because the SQL standard says so.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Kouber Saparev wrote:
> >>
> >>select timestamp '2005-09-23 23:59:59.999'
> >>
> >>I get the following result (note the value of the seconds):
> >>
> >>2005-09-23 23:59:60.00
> >
> >
> > It's the leap second.
> >
> >
>
> It is not a leap second. Leap seconds are always either on the 30th o
Nitin Tarkar <[EMAIL PROTECTED]> writes:
> Kindly guid us to export PostgreSQL Database from linux to windows.
The pgsql-bugs list is for reporting bugs; kindly do not clutter it with
help requests.
pgsql-novice might be a reasonable place for this question.
regards, tom
Alvaro Herrera wrote:
> On Tue, Oct 04, 2005 at 10:40:11AM -0400, Bruce Momjian wrote:
> > Kouber Saparev wrote:
> > > >>
> > > >>select timestamp '2005-09-23 23:59:59.999'
> > > >>
> > > >>I get the following result (note the value of the seconds):
> > > >>
> > > >>2005-09-23 23:59:60.00
> > >
On Tue, Oct 04, 2005 at 10:40:11AM -0400, Bruce Momjian wrote:
> Kouber Saparev wrote:
> > >>
> > >>select timestamp '2005-09-23 23:59:59.999'
> > >>
> > >>I get the following result (note the value of the seconds):
> > >>
> > >>2005-09-23 23:59:60.00
> > >
> > > It's the leap second.
> >
> >
Tom Lane wrote:
> Bruce Momjian writes:
> > Right. We allow leap seconds for any date/time. Are you saying we
> > should only allow them for certain dates/times?
>
> No, his point is the funny roundoff behavior.
>
> regression=# select timestamp '2005-09-23 23:59:59.99';
> timesta
Bruce Momjian writes:
> Right. We allow leap seconds for any date/time. Are you saying we
> should only allow them for certain dates/times?
No, his point is the funny roundoff behavior.
regression=# select timestamp '2005-09-23 23:59:59.99';
timestamp
Hi,
I've installed PostgreSQL 8.1 beta2 five days ago and it crashed 3 times
since then.
Here is what's been logged for the last crash
2005-10-04 11:00:19 FATAL: could not read block 121 of relation
1663/16384/2608: Invalid argument
2005-10-04 11:00:20 LOG: server process (PID 2592) was ter
On Tue, Oct 04, 2005 at 11:20:15AM -0400, Alvaro Herrera wrote:
> On Tue, Oct 04, 2005 at 10:40:11AM -0400, Bruce Momjian wrote:
> > Kouber Saparev wrote:
> > > >>
> > > >>select timestamp '2005-09-23 23:59:59.999'
> > > >>
> > > >>I get the following result (note the value of the seconds):
> >
You might want to use http://pgfoundry.org/projects/newsysviews/
instead. We've also talked about changing our naming to come more
in-line with information schema.
On Tue, Oct 04, 2005 at 01:58:36PM +0100, Tony Marston wrote:
>
> The following bug has been logged online:
>
> Bug reference:
Alvaro Herrera wrote:
> On Fri, Sep 30, 2005 at 10:37:05PM -0500, Steve Peterson wrote:
>
>>The query is submitted using the JDBC driver, via
>>the SQLExplorer plugin for Eclipse.
>>
>>Is there a way for me to see the query as it was
>>submitted to the backend? If so I'll take a look and see wh
Hi,
On Sat, 1 Oct 2005, Tom Lane wrote:
So yeah, ILIKE looks just about completely broken for multibyte encodings.
The regexp code doesn't look better, btw, just differently broken ...
So any chance to fix it before beta 3 (and also backpatch?) ?
Are you volunteering?
This stuff has neve
""Jean-Pierre Pelletier"" <[EMAIL PROTECTED]> wrote
>
> I've installed PostgreSQL 8.1 beta2 five days ago and it crashed 3 times
> since then.
> Here is what's been logged for the last crash
>
> 2005-10-04 11:00:19 FATAL: could not read block 121 of relation
> 1663/16384/2608: Invalid argument
Any known way to log at the JDBC level? When I get a little time I'm
going to write a test that bypasses Eclipse and SQLExplorer.
On Wed, 5 Oct 2005, Oliver Jowett wrote:
> Alvaro Herrera wrote:
> > On Fri, Sep 30, 2005 at 10:37:05PM -0500, Steve Peterson wrote:
> >
> >>The query is submitted us
The following bug has been logged online:
Bug reference: 1938
Logged by: Jeff MacDonald
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: FreeBSD 5.2.1
Description:pg_dump mis-intreprets "default now()";
Details:
Hi,
I did a backup from 7
24 matches
Mail list logo
